Until 4.5 I always moved notes by dragging on the note icon. Now I can't do that any more. I first assumed it was a deliberate change, but Dave has informed me that it still works on Windows, so now I assume it's a bug, and I want it back. It made it much easier to drag.
See http://community.logos.com/forums/p/44608/332331.aspx#332331 and http://community.logos.com/forums/p/44379/330420.aspx#330420.
Using Logos 4.5a Beta 2 on Mac and PC, noticing on Mac when cursor changes to hand for notes icon that drag and drop is not an option. When Mac cursor is a black arrow, then can drag and drop note, including pointer under note title text.
Keep Smiling [:)]
When Mac cursor is a black arrow, then can drag and drop note, including pointer under note title text. (italics mine)
Don't think I've tried that one before, but it very rarely seems to work on stable. Most of the time, all that happens is that the note expands, ready for input, and the cursor changes. After experimenting for quite a while I found that I could sometimes make it work, usually when I first expanded one note and then, with that still open, tried to move another. Often a second one done right after would then work as well. But I can't find a sure way to make it work. It seems very random. And in any case, the note icon is where I want to drag. Seems like the most intuitive place.
Currently Logos 4.5 SR-2 and Logos 4.5a Beta 2 are similar for many items (including SR-2 bug fixes being in Beta 2); reading plans are notably bit different (and buggy in Beta 2).
For some drag and drops with pointer under title, clicked once to focus/expand note, released mouse button, moved mouse until black arrow cursor appeared, then was able to drag and drop.
When Mac cursor is a black arrow, then can drag and drop note, including pointer under note title text. (italics mine) Don't think I've tried that one before, but it very rarely seems to work on stable.
Don't think I've tried that one before, but it very rarely seems to work on stable.
This now seems to work consistently.
This bug/regression still remains.
(And, KS4J, it also seems to be missing from the feature parity list.)
Thank you for pointing this out. I will submit this to our developers for review.
