sheepcore wrote on Nov 8
th, 2015 at 9:20pm:
Am not sure though which additional info I might give you for the issue happening all the time?
Well, the fact that you've confirmed you're using our BookMacster Button Chrome extension helps.
I played with it some more and found a bug. The bug is in the "lineage" field, which is just to the left of the
Move underlined blue hyperlink. The "lineage" field shows the selected (or newly-landed) bookmark's parent folder, grandparent folder, great-grandparent folder, etc. If I open a first .bkmslf document, then close that (or maybe not) but anyhow open a second .bkmslf document, the lineage field will continue to show the lineage of the last bookmark that was selected in the first document, which may be no bookmark, in which case it will indicate
No selection. The
Move underlined blue hyperlink still works "under the hood". This bug bears a definite resemblance to the behavior you've described. Maybe while I'm fixing it I'll discover more. In the meantime, please try to relaunch BookMacster such that the .bkmslf you want to land bookmarks into from Chrome is the first and only .bkmslf document that opens, and see if that works better.
sheepcore wrote on Nov 8
th, 2015 at 9:20pm:
On the feature request I do not want to sort a folder permanently but want to sort the current view when searching to allow me narrowing down. Keeping the columns with sort arrows for years and versions is confusing and doing so permanently across releases frustrating.
I see what you mean. The user-defined column headings were a cool way to make a flexible table back in 2009, but we can do better today, which will leave the column headings free to sort in the conventional way. I think we'll make it a priority to work on that.