Publisher: Capture changes in creation phase
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 71
- Forks
- 91
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 47
Description
Is your feature request related to a problem? Please describe.
Capture changes happene in creation phase of Publisher.
Describe the solution you'd like
Since this PR https://github.com/ynput/OpenPype/pull/4676 there is a Save button which saves changes, but without capturing changes we don't have any idea to know if there were any changes. The biggest issue is on closing the window when we should ideally ask if user want to save the changes he made -> that is not automatically triggered which is not ideal. Also we could disable Save button if there are not any changes.
[cuID:OP-5355]
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the Publisher creation phase and the Save button changes introduced by PR #4676. Determine how changes can be detected during creation and how window closing currently behaves; done means unsaved changes are recognized, Save reflects whether changes exist, and closing can prompt to save.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100