Skip to content

Fix redundant invokeLater in effective appearance notifications - #8

Open
karlvr wants to merge 1 commit into
violetlib:masterfrom
karlvr:fix/double-invoke-later
Open

Fix redundant invokeLater in effective appearance notifications#8
karlvr wants to merge 1 commit into
violetlib:masterfrom
karlvr:fix/double-invoke-later

Conversation

@karlvr

@karlvr karlvr commented Mar 25, 2026

Copy link
Copy Markdown
Contributor

notifyEffectiveAppearanceChanged() is already called from within a SwingUtilities.invokeLater in effectiveAppearanceChanged(), so the inner invokeLater was unnecessary and delayed notification by an extra event dispatch cycle.

notifyEffectiveAppearanceChanged() is already called from within a SwingUtilities.invokeLater in effectiveAppearanceChanged(), so the inner invokeLater was unnecessary and delayed notification by an extra event dispatch cycle.
@cbfiddle

Copy link
Copy Markdown
Contributor

Sometimes an extra delay is necessary. I'm not saying that is the case here, but I'm reluctant to change something that isn't broken.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants