Howard, Yes. I reported it a while ago — Bug 48892. It happens when you open or create a new comp via the File menu - after you already have a comp open.
Here are the replication steps I sent to The Foundry: >> Software & OS: >> Nuke 9.0v4 >> Windows 7 Professional >> >> Bug: >> User not prompted to save modified comp when comp is opened or created from >> first script's File menu. >> >> Reproduction Steps: >> 1) Launch Nuke and save two simple Nuke comps and quit Nuke. >> 2) Launch Nuke, open the first comp.. >> 3) Then, use File/Open Comp to open the second comp... >> 4) Modify the second comp... >> 5) Quit the modified comp... >> ** You are not prompted to save! ** >> ** This problem also occurs if you use File/New Comp or File/Open Recent >> Comp. >> Basically, any time you open or create a comp from an existing comp's File >> menu! ** Rich Rich Bobo Senior VFX Compositor Armstrong White Email: [email protected] http://armstrong-white.com/ Email: [email protected] Mobile: (248) 840-2665 Web: http://richbobo.com/ "When we do the best we can, we never know what miracle is wrought in our life, or in the life of another." - Helen Keller > On Jul 24, 2015, at 12:34 PM, Howard Jones <[email protected]> wrote: > > Anyone else seeing Nuke quit without prompting to save an unsaved script. > > It’s not all the time and I haven’t figured out the cause yet > H > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
