On Nov 22, 2013, at 16:07, Hendrik Schreiber <h...@tagtraum.com> wrote:
> On Nov 22, 2013, at 14:51, Hendrik Schreiber <h...@tagtraum.com> wrote: > >> [...] > > I should add that this only happens with DPI scaling. > And since the images didn't make it through, here they are: On second thought, perhaps the 16 pixels Table.rowHeight is the correct approach. And scaling up fonts to be a lot larger (as it happens in Win L&F) is what's wrong. Because it violates write once, run anywhere. On OS X you guys have been struggling to implement MultiResolutionImages and the like, so that if the physical display resolution is high, Java can automatically render a high resolution version of a given image. In the same spirit the L&F font sizes aren't suddenly changed, but instead they are rendered with greater detail. Because we use a virtual desktop resolution. Now, if on Windows with Windows L&F suddenly all fonts are a lot larger, but images are still the same size (status quo) and in relation to labels way too small, things look out of proportion, layouts are broken. The OS X solution allows for seamless migration, even if the programmer does not supply MultiResolutionImages. The current (1.7.0_45) Windows L&F does not allow this. And regardless which approach is better: Shouldn't both L&Fs use the same approach?! If you agree and have access to the Oracle bug database, please add this opinion as a comment (Oracle bug id 9008405). Or better—talk to the guys in charge of Windows L&F. Thanks, -hendrik PS: I hate the fact that I cannot see the bug I filed anywhere and add comments to it myself. Or can I?
