Full-screen toggle; command-Z

[KB]

Hi Brian,

1. When toggling between full screen mode and the regular view, adjusted window layouts are lost as soon as I toggle. So, using command-control-F, I go to the full screen view, I have to mouse around to Window>Layouts> and then the saved layouts if I want my windows back.

I’m not quite sure what you mean here, could you explain further? Just leaving full screen should return you to normal mode with the same set-up, unless you launched full screen mode using a layout, in which case returning to normal mode will restore its previous layout.

2. I saved my layout for full screen screenplay, but this layout does a couple of funny things: a.) it gets rid of the red line at the top of the red and blue index card I’ve selected, and allows me to scroll up endlessly, and it hides the top two lines in the Binder and the top two lines in the Editor. I can only see what’s up there if I scroll and hold them manually - as soon as I let go, they’re gone. This only happens with my saved Full Screen layout.

This sounds like a bug that should have been fixed for the next update. Please try downloading the beta version here and see if that addresses it:

https://forum.literatureandlatte.com/t/scrivener-2-x-update-betas-download-here/11262/1

2. When there is more than one Scrivener project open, and command-Tab is used to go to another program, when I return, Scrivener decides which project to bring to the front, and it’s not necessarily the project that was open when tabbing away.

Unfortunately this is out of Scrivener’s hand - OS X chooses which project to bring to the foreground. If you command-tab out of Scrivener with a project in full screen mode and command-tab back, for instance, OS X doesn’t move back to full screen but shows the project that’s at the foreground on the current screen. I find this behaviour annoying myself, but as I say, application-switching behaviour is handled by the operating system.

Separately, it would be nice if command-Z to undo were available in the Binder after moving something. I bet you have a good reason why this is, and I’ll probably be embarrassed at not having seen it somewhere.

For various technical reasons, the binder undo stack gets cleared when the document in the editor changes. If you lock the editor so that the document doesn’t change there while moving things around in the binder, undo continues to work. It’s down to the way everything is interconnected and the fact that in Cocoa, undo works at the view level rather than the data level, so once something has been swapped out of a view, the undo stack that was working with it becomes invalid. Fortunately there’s a way to change the undo stack for text views, so that each text has a separate undo stack, but sadly this isn’t possible for the binder; or at least, I haven’t yet found a way of doing it that doesn’t cause many more problems. I agree that this would be a good improvement for the future though.

Thanks and all the best,
Keith