-
-
Notifications
You must be signed in to change notification settings - Fork 265
-
-
Notifications
You must be signed in to change notification settings - Fork 265
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
Windows with Decorations: Double Titlebar when Re-Opening JFrame Instance #277
Comments
Interesting... will try to reproduce. Do you use |
Is there anyway to disable Decorations for just this window with the new Decorations setup until this bug has been fixed? |
Nope, I don't use either of those on this windows. |
No, but this is a good idea 👍 Can reproduce the issue. Working on a fix... Will release FlatLaf 1.1.1 in a few days. |
Great, glad it was easy to reproduce! Thanks so much for your super fast response on this! |
…isposing a window and then showing it again (issue #277)
Yes, it was easy 😉 window.dispose();
window.setVisible( true ); Fixed in main branch. Please try the latest 1.2-SNAPSHOT and let me know whether it now works: |
…s per window via client property (issue #277)
All appears to be working correctly and looking great with Decorated titlebars in Windows with the latest Snapshot (flatlaf-1.2-20210323.141150-4.jar). Thank you! |
I have just updated to FlatLaf 1.1 and have noticed an issue with a loading window that I use. It is a JFrame which gets instantiated once and then is disposed and setVisible multiple times throughout running the app.
The first time this loading windows opens, everything looks fine. But, when this window is disposed and then re-opened, it gets 2 titlebars. One appears to be the undecorated titlebar, and the other is the FlatLaf decorated titlebar.
Screenshot attached. Please let me know if there is any other info or testing you need from me. If it turns out to not be easy to reproduce, maybe there is something else weird I am doing that I can try to investigate further.
The text was updated successfully, but these errors were encountered: