Open rawles opened 7 years ago
I noticed that even though the grid disappears, any control codes on the screen stay, even when the status bar is hidden. Maybe people want this, to show how control codes work... Hmm...
tries to imagine On the one hand, perhaps a user just wants to get a glance at the final product several times whilst in the middle of editing with the help of grid and codes. On the other hand, perhaps they enabled codes after some preliminary grid work and want the codes to remain.
Argument for hiding both: If I'm a 'glancer' it'll drive me mad several times a session having to hide two things. If I'm a 'prelim' there's just the one irritation of having to put the codes back on.
Argument for not hiding both: Coding it for a 'glancer' makes no sense because you'd have to re-enable codes next time the grid is toggled, which is seems really weird. 'toggle grid' becomes 'toggle UI.' It might make more sense to change 'hide status bar' to 'toggle UI' (or 'toggle extras' or something) and the 'glancers' and 'screenshotters' can use that to toggle grid, cursor, status bar, codes all in one swell foop.
When people hide the status bar, it's usually because they want to capture the screen, even though this is now possible with Esc-E. In any case, the grid should disappear when the status bar is hidden.
Thanks to @ZXGuesser for spotting this.