Feature: added start locked preference option#482
Feature: added start locked preference option#482Bora-Valar-Kara wants to merge 2 commits intolacymorrow:mainfrom
Conversation
- Added startLocked checkbox to System Settings - Function: On startup, startLocked forces hidden.locked = true (overrides startUnlocked) - Fixed duplicate 'dialog' declaration in menu.js
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a new 'Start Locked' preference, giving users more control over the application's startup behavior. It also rectifies a code duplication issue, contributing to overall code quality. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces a 'start locked' preference, allowing the application to launch in a locked state. This new option correctly takes priority over the existing 'start unlocked' setting. The changes include updating the default preferences, adding the new option to the settings UI, and implementing the startup logic. Additionally, the pull request resolves a variable naming conflict in menu.js. The changes appear correct and align with the pull request's goal.
True. I overlooked this it seems... (I checked more than once even...) I just started learning JS and I was tinkering around. Very nice app! I'm a regular user! |
|
Well, I appreciate you taking the time to make a pull request! There's a new version of crossover I'm testing out if you would like to take a look and beta test (need to add windows/linux builds still): https://github.com/lacymorrow/crossover/releases/tag/v4.0.0-beta.1 |
|
Oh, and you caught a bug that I overlooked also. Well done, I appreciate it. Just added Windows/Linux builds to the beta release: https://github.com/lacymorrow/crossover/releases/tag/v4.0.0-beta.1 |
Oh yes! It's small but I hope that was helpful! |

QoL feature. On regular use, locking in place every time you boot becomes redundant.
Please let me know if this change is something you would want in your upstream.