🎨 Palette / 🛡️ Sentinel: Consolidated UI and Action Button Batch - #229
Conversation
Connect the model_changed signal to _update_action_buttons and initialize the state on startup to prevent users from triggering actions when no model is selected. Co-authored-by: dieterolson <198168927+dieterolson@users.noreply.github.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a2ab70310e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| self.resize(900, 680) | ||
| self._build_ui() | ||
| self.setStyleSheet(build_stylesheet()) | ||
| self._update_action_buttons() |
There was a problem hiding this comment.
When the app starts with a discovered model but no llama-cli, this new initialization call disables both launch buttons. If the user then successfully builds the executable through SetupDialog, _open_setup_dialog() returns without calling _update_action_buttons(), and the only new refresh trigger is a model-selection change; with a single already-selected model, both buttons therefore remain disabled until the application is restarted. Re-evaluate the button state after the setup dialog closes or when its build completes.
Useful? React with 👍 / 👎.
1 participant
Consolidated batch incorporating changes from PR #227 and PR #228. Closes #220, Closes #221, Closes #222, Closes #223, Closes #224, Closes #225, Closes #227, Closes #228