3 ms·
The value depends entirely on specific conventions, but you've mentioned none. There is also value in consistent UI across platforms (which native UI don't supp
by eviks 6mo ago
The value depends entirely on specific conventions, but you've mentioned none. There is also value in consistent UI across platforms (which native UI don't support) as for some conventions you'd prefer to ignore the OS defaults.
- saratogacx 6mo agoNot OP but I have a similar complaint. The two primary OS items that turn me off of zed are not being able to have a title bar and the fact that menus open on hover and not on click. VSCode, and IntelliJ let me turn on OS level title bars so I can handle the window without needing to try and find the magic spot not filled by some other app based nonsense as well as making it easier to see what window is active. Menus can be unrolled from the hamburger but now pop open if I just swing my cursor through. I've no idea what convention that was pulled from but I think they just took the hamburger menu event triggers and left them as they were instead of changing them to act like an OS menu is expected to function. I'm sure there are others that I'd find using the app but just those two was enough of a personal issue for me to just not bother.
- eviks 6mo agoGood illustration - if you have a more ergonomic window management workflow that doesn't require hunting for a tiny bar at the top, have a custom more prominent active window indicator, and use keyboard to navigate menus, these are less of an issue.
- nielsbot 6mo agoI definitely hate the non standard context menus that can’t render outside of their containing window. (And when they can’t turns out they can secretly be scrolled up and down) Yikes.