[Remote rendering 3.4] UI panel and theme state authority

Aperta

#22 aperta il 25/8/2026 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@LKasianAnsys ci sta già lavorando.

Dal 11/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

technical

📝 Description of the feature

Design question: do we want to sync the UI state to the server, so it can stay up to date, or do we want this to remain client-owned entirely?

Today, at save_state time, the UI state, like the rest of the state, is retrieved by the server through a client round trip. Do we want to continue this pattern for the UI state, which is independent of the VTK pipeline? Or do we want to use a sync-back pattern like the camera, and store the UI state metadata on the server, so that save_state doesn't require a client round trip, and so that a refresh or reconnect will preserve the UI state as well as the VTK pipeline?

If we want to keep the UI state purely client-side, there is no work here.

If we want it to be synced back to the server, then the TheiaUIState (panel collapsed/expanded, active tab index, dark/light theme) flows through the same save/load paths as camera and per-part state.

More details to be added in backlog grooming.

Acceptance Criteria

No in-visualizer behavior changes.
Refresh behavior depends on the decision that gates the rest of this user story.

💵 Business Value

No response

🔗 Useful links and references

No response

Lingua principale: Python
Stelle: 1
Fork: 0
Merge medio: 1g 21h
PR unite (30g): 47

Guida per i contributori

Apri la guida per i contributori

Come iniziare

Leggi tutta la issue e poi la guida ai contributi del progetto.
Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
Fai un fork del repository e lavora su un branch.
Apri una pull request che faccia riferimento al numero della issue.