sublimehq / sublime_text

Issue tracker for Sublime Text
https://www.sublimetext.com
814 stars 40 forks source link

Distinct menu shown/hidden state for F11 (full-screen) mode #728

Open qgates opened 9 years ago

qgates commented 9 years ago

Normal and distraction-free modes remember their menu shown/hidden state per-project, which is great. However, Full-screen (F11) mode shares its menu shown/hidden state with normal (windowed) mode, which is a PITA.

Could we have the menu state remembered for F11 mode as it is for distraction free mode?

(Tested in Windows/Linux, Sublime 3, latest builds as of this post)

FichteFoll commented 9 years ago

I don't quite follow. Do you man the "Enter Full Screen"/"Exit Full Screen" menu item? What are steps to reproduce, what is happening and what do you suggest instead?

qgates commented 9 years ago

Yes, Enter/Exit full screen (which maps to key F11).

If, for example, I have the menu visible in normal (windowed) view, switch to full screen (F11), then hide the menu using the command pallette, when I return to windowed view the menu remains hidden. If I re-enable the menu in normal mode, and switch to full screen, the menu is now visible.

Contrast this with distraction free mode, which remembers the menu view/hidden state independently. What I'm asking/suggesting, is that full screen mode remembers the menu view/hidden state in the same way as distraction free mode does.

Presently, I find myself repeatedly having to hide the menu in full screen mode, then unhiding the menu in normal mode. Implementing the above behaviour has no negative effects (that I can see) and is more consistent: Sublime will remember the menu shown/hidden state for normal, full and distraction-free views, per project and globally.

FichteFoll commented 9 years ago

Ah thanks, now I understand. This definitely makes sense.

VipSaran commented 7 years ago

Something more in the context of Distraction Free mode: apart from it remembering its last setting for menu_visible, the app should respect menu_visible also when it's specified in "Distraction Free.sublime-settings" file. What's more, that way should have priority over remembering what last was used in the same mode (as that should be regarded just as a workaround solution until "Distraction Free.sublime-settings" file was introduced).

Discussion: https://forum.sublimetext.com/t/distraction-free-mode-customization/7177