ID 392475 - crashFile: Immediate autosave when maximising Katana after an idle period longer than the save interval

Problem summary:

When the preferences/crashFile/time setting is set to a given interval, it will save correctly when the user is interacting with a Katana session. When the user leaves the Katana UI minimized for a period longer than the time interval, it is only when Katana is maximised again that the autosave event will trigger.

This has been flagged by customers as a source of annoyance to artists switching context between Nuke and Katana, and having to wait for the autosave to complete before continuing their Katana work.

Steps to reproduce:

1. Change preferences/crashFile/time to 1 minute, (also set numberOfActions to 0)
2. Open a project and change view and edit flags on random nodes, so the project is now in an unsaved state
3. In a minute, an autosaved version should appear in your crashFile directory (tmp by default on linux)
4. Change view and edit flags again on random nodes, minimise Katana
5. Leave Katana idle for over 1 minute
6. Maximise Katana

Expected behaviour:

• Autosave continues while Katana is minimised and in an unsaved state, or;
• "clock is stopped" when Katana is minimised, and is started again when Katana UI is reinstated. (eg, interval is 5 mins, Katana is idle/minimised after 1 min, at the point it is reinstated, 4 mins remain before autosave is triggered) 

Actual behaviour:

Autosave is triggered as soon as Katana UI is reinstated if it was left idle longer than the autosave interval

Workaround:

No known workaround.

Tested versions/platforms:

• 1.0v1 - Affected

Customer version/platform:

Not supplied