Tony Stout wrote on Apr 20
th, 2010 at 12:49am:
when the menubar icon is displayed, if there is no browser open, i get a "no browser" dropdown. seems a browser (any browser) must be running to be able to view the bookmarks.
Although I believe that is indeed the way BookMacster is designed, I understand that the behavior may be unexpected. I've entered this new little issue into our bug tracker for investigation.
Tony Stout wrote on Apr 20
th, 2010 at 12:49am:
anyhoo, after downloading 0.9.26 and opening my data file, i was able to uncheck the 'safari' client without issue. however, when i removed it altogether, i had to save twice (which signalled the issue before). i did a revert and the data file was restored without the client listed.
By "need to save twice", I presume you mean that the red button in the title bar was still "dirty", and you got an "unsaved changes" warning if you attempted to close the document. I've seen this myself recently. This little issue is now entered into the bug tracker also.
Tony Stout wrote on Apr 20
th, 2010 at 12:49am:
with the throttle set to 1 second, the verify completed successfully. i re-ran the verify with the throttle set at 10 and it then completed successfully. not sure if the initial verify fixed the offending link, but it seems to be smoothly running now...
Unfortunately, I don't think it's a simple offending link any more. I tried to reproduce the crash on a Mac like yours at Apple's lab yesterday using your Bookmarkshelf. But it verified 20 times with no crashes. Maybe you've got some other system extensions that are a factor. When you have a minute, please in the menu click ▸ About This Mac, then click the "More Info" button. System Profiler will launch. Click in the menu File ▸ Save and save as an .spx file. Then go do something else; it will take several minutes to generate the file. When done, send me or attach to this thread the .spx file it will produce.
I have a similar report from another user, using Bookdog, but was unable to reproduce that crash also. It may be due to some interaction between Mac OS X and the traffic-shaping policies of your internet service provider. Another developer has reported some new bug(s) in the URL loading system of Mac OS X 10.6.3 which have affected other apps. Indeed, we'd went several years without a crash report in Bookdog's Verify, then when Mac OS X 10.6.3 is released we get two, and I was able to crash BookMacster once with my own bookmarks.
If anyone else sees such a crash during Verify, I'd appreciate the Bookmarkshelf file, .spx file, and also tell me what type of internet service you have, how long into the verify before it crashes, and any other interesting tidbits.
We might reduce the maximum value on that throttle setting.
Thanks again!