*speechless* *kudos*

Oh … we finished it last night.  Sorry, forgot to post here!

BookMacster and Synkmark 2.0.6 are now available on the beta channel.  Has two Inspector issues fixed.  I hope that one of them is the issue you reported!

Thank you for your patience, sheepcore.  The way I've found to reproduce the problem is to launch BookMacster in the background, then Show BookMacster, which should show .bkmslf document and Inspector, then Background BookMacster.  It is the backgrounding which causes the Inspector's Lineage field (the thing that shows No Selection and also its Tags field to become unbound from the bookmark data model, so that the Lineage field indicates, usually, No Selection, although it can also remain stuck showing the lineage of the last bookmark whcih it was bound to before the backgrounding.

So, as a workaround, don't use the Background BookMacster menu item in the menulet.  If you really need to, relaunch BookMacster when you're done.  I hope this issue is the same issue that you found.  We've now finished the fix but have not published yet.

Sorry, this issue got pushed aside in favor of the new Chrome extension thing.

Last night, I was able to reproduce, understand and put together a proof-of-concept that fixes it.  The issue was due to a small bug in Apple's token field (the thing that displays the tags in the blue bubbles), which we had worked around using a messy kludge several years ago, which stopped working, I think, in El Capitan, not BookMacster 2.x.

We should have version 2.0.6, with the fix, out in the next couple days.

sheepcore wrote on Nov 14^th, 2015 at 5:47pm:
Yes, I see what you mean.

While I was trying to reproduce the No Selection thing, I found that as you said the Inspector was not always appearing.  Different but related problem.

So, the good news that I've decided to rip out that whole try and do what you want mechanism.  It might get replaced with a manual preference, as you prefer.

The bad news is that this is going to take some time, because I'm also in the midst of clearing warnings which popped up when we changed our apps' Deployment Target from OS X 10.8 to OS X 10.10.   Developers call it the Apple treadmill.  It's a time sink, but it pays off in the long run.  There were 95 warnings a week ago and we've now got it down to 33.

sheepcore wrote on Nov 14^th, 2015 at 5:47pm:
No.

sheepcore wrote on Nov 14^th, 2015 at 2:48pm:
Thank you very much, because I tried it a few more times, then gave up and moved on to other issues.

sheepcore wrote on Nov 14^th, 2015 at 2:48pm:
Yes.  The idea is that BookMacster tries to remember what you like.  If the Inspector is open when you quit BookMacster, then, during the next launch, BookMacster re-opens the Inspector when the first document is opened.  If the Inspector is closed when you quit BookMacster, then, during the next launch, BookMacster does not re-open it when the first document is opened, which you may have, even though you can't see it because you've done a Launch in Background  Try to remember to close the Inspector before quitting.  I just tested this and it works, even if you are using Launch in Background.

OK, trying the rest of your procedure, I am able to reproduce problems.  Not exactly as you said, but I have enough to bite into into now.  I'll be back after I've found something.

sheepcore wrote on Nov 14^th, 2015 at 2:48pm:
I have not seen that, but will keep on the lookout for it.

sheepcore wrote on Nov 14^th, 2015 at 2:48pm:
I don't see that in my previous posts, but it doesn't matter because the answer is "no".

sheepcore wrote on Nov 14^th, 2015 at 2:48pm:
Is that another feature request for Bookmark all tabs?

Indeed, that No Selection is what I saw Sunday night.  It means that the field did not get "bound" to the selection (the new bookmarks).  I just wasn't able to make it happen yesterday.  We'll both keep trying.

Bad news, sheepcore.  Although I did not fix anything, I can no longer reproduce the problem I saw last night.  I have been trying for 25 minutes, launching and quitting BookMacster, opening and closing documents, and landing bookmarks from Chrome, and every time, the Inspector and the lineage view have worked perfectly.  Please relaunch BookMacster and make a note of each step you do to reproduce the problem.  Something like this:

• Launch BookMacster
• Some .bkmslf document opens/not automatically
• Inspector window opens/not automatically
• Activate Chrome.
• Visit a website.
• Click the BookMacster button in Chrome with/out holding down option key.
• Result: …