4 ms·
One of my biggest issues is that "flat design" by definition also dictates "borderless". Meaning, a dialog or other window adjoins or overlaps another, you some
by bityard 2y ago
One of my biggest issues is that "flat design" by definition also dictates "borderless". Meaning, a dialog or other window adjoins or overlaps another, you sometimes need to stare for a few seconds to tell where one window begins and another ends. Seems to be worse on Windows and Chrome, but I see it on Linux sometimes too and try to file a bug when it happens.
Adding at least a 1-pixel border and drop shadows to all windows can go a long way to fixing this, but I don't believe that the latter helps "dark mode" users much.
(Of course, a lot of developers these days only use and develop apps and websites in full-screen mode on a tiny 13" laptop screen, so they never see a lot of the issues that "flat" causes.)
- p_l 2y agoA lot of oldest GUIs were flat by hw limitations (often 1bpp displays) and they absolutely didn't dictate borderless. Sometimes there wasn't an "always on" border, but a border would show up when your mouse was over a clickable element, sometimes there was a border. Activation of UI element was often done by swapping foreground and background colour, something that was immediately visible.
- em_te 2y agoI think windows were flat on Windows 3.1 too and only adopted the 3D raised borders starting with Windows 95.
- p_l 2y agoWindows 3.0 brought "3d" styling to windows, actually - where available at least. Windows 2.0 had some simple shading or rather "complex borders" if you had colour display, but nowhere close to 3D shading of 3.0