-
-
Notifications
You must be signed in to change notification settings - Fork 280
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
Layout loop caused by FlatTitlePane #420
Comments
Thanks for reporting/debugging this issue. I've added the call to It was necessary to update the layout when adding components to the menu bar. With test app Before: With Without Anyway, need to find a solution without |
Replacing Could you please add |
Just checked with one of my UI tests where the layout loop was always reproducible and calling |
(cherry picked from commit d3355ed)
Fixed in 1.6.2. Thanks. |
I'm hitting a layout loop that is triggered by
FlatTitlePane::menuBarLayouted
callingrevalidate()
thereby somehow triggering a layout on the JRootPane. I'm not sure how this can happen, but I see this deterministically in some places in my automated UI tests that use AssertJ Swing as a framework. The async stack trace chain in IntelliJ looks like this:and continues like that until IntelliJ truncates it. When this layout loop is triggered for the first time, it continues until the frame is closed. I notice this because the testing framework will become extremely slow in this case. The custom repaint manager in the stack trace is just for me to set a breakpoint, it also happens without it.
Passing the VM parameter
-Dflatlaf.useWindowDecorations
prevents this problem, but this is obviously not desirable.My workaround is to set
with
which effectively just removes the
revalidate()
call fromFlatTitlePane::menuBarLayouted
. I don't see any negative effects from that removal.The text was updated successfully, but these errors were encountered: