step 2: add gauge state sizing and animation model
This commit is contained in:
@@ -8,12 +8,13 @@ There is no Step 0. Initial setup is listed separately, then implementation star
|
||||
2. Always read `codex/FEATURES.md`, `codex/ARCHITECTURE.md`, and `codex/AGENTS.md` before making code changes.
|
||||
3. Keep `codex/AGENTS.md` as a rolling log of what has been done, what is broken, and what comes next.
|
||||
4. Update `README.md` and `docs/` whenever public behaviour or examples change.
|
||||
5. After every step, update `codex/AGENTS.md`, run relevant checks, and commit if working in git.
|
||||
5. After every step, update `codex/AGENTS.md`, run relevant checks, and commit the completed step when working in git.
|
||||
6. Do not casually change public API once introduced.
|
||||
7. Dear PyGui calls must happen on the GUI thread only.
|
||||
8. Runtime gauge updates are GUI-thread-only unless explicitly documented otherwise.
|
||||
9. Prefer stable, boring implementation over clever drawing tricks.
|
||||
10. Keep each step shippable and tested before moving to the next.
|
||||
11. Do not start the next step while the previous completed step is still uncommitted.
|
||||
|
||||
## Initial setup instructions
|
||||
|
||||
|
||||
Reference in New Issue
Block a user