Issues having to do with floating panels and layouts
There seem to be quite a number of UserVoice suggestions having to do with the way floating windows work. I'd like you to consider addressing as many of these as possible in an upcoming release soon.
The thing that bugs me most and has been a problem since the beginning of L4 is that when you float a window and then go back to your main layout and open another resource, it gets opened in your floating window instead of in one of the panels that are in your main layout. This is especially irritating when you've opened a resource in a floating panel and then put it into Reading View. You're working on reading a book, say, and you want it to fill the entire screen while you're reading it, but you also want to be able to Alt+Tab back to your Logos layout to do something else (multitasking). If you open another resource while you're "doing something else" it is particularly annoying when it opens in the same panel as the resource that's in Reading View. It doesn't happen all the time. It's unpredictable. Seems to have something to do with Logos's intelligent algorithm for figuring out what panel to open a new resource in. But it should never open a new resource into an already floating or Reading View panel. I've added a new UserVoice item for this.
Here are most of the UserVoice items that deal with floating/docking windows, layouts, and opening resources:
EDIT: Also review forum threads that come up in this Google search: annoying open "floating window" site:community.logos.com
Comments
-
Rosie Perera said:
The thing that bugs me most
The thing that bugs me most with floating windows is Logos never remembering that I always want them full screen. Especially Library.
Number two would be opening in the wrong window.
Number three would be docking to some completely different place than where I floated it from.
Rosie Perera said:it should never open a new resource into an already floating or Reading View panel
That is not altogether correct. If I open from the main window, no, it shouldn't, but if I open from a floating window, it should.
Say I'm working in a floating window and Shift-Cmd-S to open a Search, then it's extremely annoying when it opens in a tiny tab in the main window (which it does), and I have to move the window down and drag it to the floating window (and then at some point move the window up again).
Or say I'm tagging books in a floating Library window, and need to open one to decide how to tag it. Then, again, it's very annoying when it opens in the main window instead (which, again, it does). Slightly less annoying, as in this case I can close it after looking and don't have to drag it to another window. But on the other hand also more annoying, as in this case Logos doesn't even switch to the other window, but leaves me wondering if the book has opened at all, and forces me to go there manually to check. Plus I usually have to drag it anyway, as the panel it's chosen to open in always seems to be the smallest one.
[:'(][:'(][:'(][:'(][:'(]
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:Rosie Perera said:
it should never open a new resource into an already floating or Reading View panel
That is not altogether correct. If I open from the main window, no, it shouldn't, but if I open from a floating window, it should.
Good point.
0
