Hi Mike, also maybe double-check what you have put in as the shortcut key for full screen.

Have you possibly copied it to the commands sub-folder? If so move it out from there, you can put it into a scripts folder somewhere, and then in the shortcut key put the entire path to the script file like "c:\scripts\FullScreen.js", and _not_ just the name FullScreen like is done for commands.

Does that then solve this start-up anomaly for you?

My guess is that maybe you were getting it launched as a "command" instead of as a script, which are managed in slightly different ways - commands have some other things that happen for them part of which is handling that sub-palette stuff.

- Michael