Skip to content
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

Fix default look-and-feel in settings dialog #3226

Merged
merged 1 commit into from
Jul 26, 2023

Conversation

flo2702
Copy link
Member

@flo2702 flo2702 commented Jul 26, 2023

When first started, KeY uses the Java cross-platform look-and-feel called Metal. But opening the settings dialog automatically selects the System look-and-feel as default.

Thus, when installing KeY on a platform that provides a system look-and-feel, you will see the Metal LnF at first, but as soon as you generate a settings file by opening the settings dialog, KeY will switch to the System LnF even if you don't select anything.

This PR fixes this by always applying Metal as the default.

@flo2702 flo2702 added this to the v2.12.0 milestone Jul 26, 2023
@flo2702 flo2702 requested a review from wadoon July 26, 2023 12:14
@flo2702 flo2702 self-assigned this Jul 26, 2023
@flo2702 flo2702 marked this pull request as ready for review July 26, 2023 12:15
@wadoon wadoon merged commit 1bae5e5 into KeYProject:KeY-2.12.0 Jul 26, 2023
5 checks passed
FliegendeWurst added a commit to FliegendeWurst/key that referenced this pull request Jul 27, 2023
@FliegendeWurst
Copy link
Member

Thus, when installing KeY on a platform that provides a system look-and-feel, you will see the Metal LnF at first, but as soon as you generate a settings file by opening the settings dialog, KeY will switch to the System LnF even if you don't select anything.

Interesting, on my system it was the other way around (first System, then Metal). My fix 614852f in #3216 ensures that Metal is explicitly set when starting KeY.

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

Successfully merging this pull request may close these issues.

3 participants