-
-
Notifications
You must be signed in to change notification settings - Fork 268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filechooser "Desktop" view shows incorrect details for user folder #249
Comments
Looks funny. Occurs also in Metal and Nimbus. And for "OneDrive" folder. |
It gets worse! Wait: |
Okay, this one is a bit more annoying. It looks like the filechooser somehow has overlapping columns or so. Same thing though, seems to affect all look and feels. Again, I am sure flatlaf isn't the right place for this, but I hope we can do something anyways. |
Strange, have this too... |
I guess I can try this out with java 15 tomorrow. Maybe it's already fixed 🤷 |
I have it in Java 15. There are some strange characters in the date. BTW the column headers are also wrong. |
… selected in "Look in" combobox (Windows 10 only; issue #249)
Regarding the strange dates in the last screenshot:
They come from native method They are also visible in Windows L&F, but not in Nimbus or Metal. Seems to depend on the used font. This can be reproduced in FlatLaf Demo: in menu use "Font > Dialog" to change font to Dialog, open file Anyway, implemented a fix that removes those characters in commit 5b65ed8 |
Regarding the initial issue, data displayed in wrong columns, this is a Java bug. |
Fair enough. Thank you :) |
So, first, let me mention that this is not a flatlaf bug, since it's broken in the Windows L&F as well, but maybe it's possible to work around this issue, as I doubt that such a trivial swing bug will ever get fixed.
This happens when you switch to the details view and select "Desktop" in the combobox.
So, for some weird reason the user folder is shown with an "element typ" that actually a date, but should be something like "Folder" or even empty.
The text was updated successfully, but these errors were encountered: