Some users complained that the interface of DEVONthink 2 was unattractive. I have tried to identify any changes in the final release that affect any of my points, but if I catch anything later I’ll be sure to update this post. Please note that these opinions were formed using the betas. Now, though, DEVONtechnologies has released an entirely new version of DEVONthink for the Mac.ĭEVONthink 3 is too deep of an application for me to cover all its features, do it justice, and still live my life, but here are some bullet point highlights of my favorite additions and changes, after using the DEVONthink beta for the past few months. I’ve been using DEVONthink 2 for over 7 years, during which time the program has seen frequent updates and improvements. I use it as a central repository on my Mac for almost every piece of information in my professional and personal life, including as a place to store personal and business records, deposition data, jury verdict reports, legal research, trial notebooks, and more. I believe that setting the Smart Rules to “after saving” will resolve the issue for my setup, since they will no longer be triggered at the same time after opening the database following a “Missing File” message and automatic repair, which seems to cause the issue.Readers of this blog know how important DEVONthink is to my workflow. But only after repairing a missing file error. It seems that DT runs interval-based smart rules immediately upon opening the database, and that if two smart rules contain the same script this causes the spinning wheel issue. If I set the smart rules containing the same AppleScript to “After Saving”, then I can import them with the database open and there is no spinning wheel.However, this is only the case, if these smart rules are also set to run in intervals (Hourly, every minute, etc.) If, with the database open, I then import two smart rules containing the same apple script (applied under different conditions), then I get the spinning wheel.After exporting and removing all AppleScript smart rules, the database opens normally and there’s no spinning wheel.However, I believe come closer to identifying the cause, and mitigated it for my specific setup. The issue has reoccured twice, each time after verification found missing files. But I’m just really happy that everything is fine, and it seems pretty clear that this was not caused by an issue in DT as such.Ī huge thank you goes to for your help! I never would have guessed it’s an issue with apple scripts I’m using in smart I wanted to provide an update on this, in case it’s useful or it helps to identify a causal factor. The mystery remains, why script-based Smart Rules that worked fine over the past months suddenly caused an issue. I’m confident that this is solved, since standard restoring and rebuilding has always been super reliable when I needed it in the past. I believe that the database itself is fine, and will go on to verify this now. So it seems that the reason only this database caused the freezing is that the Smart Rules containing apple scripts all have just this database in scope. To test whether this would solve the freezing, I tried setting all SmartRules to OnDemand before opening the database in question. Yes, several of my smart rules do use embedded apple scripts, although I did not change any of them recently. I have also rebooted several times.Īny troubleshooting suggestions are most welcome and appreciated. I have now uninstalled Adobe Acrobat just in case, this did not help either. There was actually a warning in DT, that the Adobe viewer plugin is incompatible, which I initially disregarded. The only thing that changed on my system is that I installed Adobe Acrobat Pro 2020 yesterday. BUT: The issue persists with that version of the database as well! So I tried restoring a previous version of the database that I know worked flawlessly before and certainly was not corrupted when the backup was made. Whenever I open this database, the same behavior reoccurs. There was neither a crash, nor did DT “unfreeze” and become operable again. However, at this point DT just froze completely (spinning wheel). Upon clicking “repair”, the message said that repair has been successful. Today, upon opening said database, verification said there was one inconsistency. I’ve encountered the occasional issue in the past, which was easily solvable by restoring my main database via TimeMachine, but this one has me a bit worried:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |