I note that with the latest versions, when you make a change in the editor you don't seem to be able to use that change in the current session without saving it to the cue file. This is a problem as I often have to make temporary changes to a cue for the current run only - I don't want the file on disk changed. Older versions of SCS allowed this - changes were applied to the current session and if you did not explicitly save them, you had the option when closing the program of saving changes or not. Please can this behaviour be restored? Or have two buttons - save to current session and save to file?
Also, I use a dual-monitor setup and like to have the run screen on the left monitor and the editor in the right - pleasecan you retain the editor window positioning both within and between sessions? At the moment it always opens centered which means it's half on one monitor and half on the other!
Thanks,
Dave
Editor - "save" option for current session only (in 10.1.0)
-
- Site Admin
- Posts: 3630
- Joined: Sun Jul 24, 2005 8:58 am
- Location: Brisbane, Queensland, Australia. TZ:GMT+10
- Contact:
That shouldn't be the case. Any change made in the Editor should be immediately effective in the Run Screen. Only if you Revert or Cancel should the previously saved settings be reinstated. Can you give an example of what doesn't appear to be made effective until you Save?I note that with the latest versions, when you make a change in the editor you don't seem to be able to use that change in the current session without saving it to the cue file.
Good suggestion to retain the Editor position between sessions, particularly for a dual-monitor setup.
Any change at all. Eg in the demo, change the hot key for the one of the cues, it does not change in the window unless I save before of when closing the editor.
Or insert a cue - it appears in the run window until I close the editor, then it vanishes.
Or re-order a cue - the cues move in the run window and then when a close the editor withotu saving, they snap back where they were.
I'll try a full uninstall- reinstall and see if that helps....no it doesn't
Or insert a cue - it appears in the run window until I close the editor, then it vanishes.
Or re-order a cue - the cues move in the run window and then when a close the editor withotu saving, they snap back where they were.
I'll try a full uninstall- reinstall and see if that helps....no it doesn't
-
- Site Admin
- Posts: 3630
- Joined: Sun Jul 24, 2005 8:58 am
- Location: Brisbane, Queensland, Australia. TZ:GMT+10
- Contact:
I'll do some testing of what you have explained. It sounds as if clicking the Close button isn't asking you if you want to save your changes. However, with 9.2 it is now not necessary to actually close the Editor. When the Editor is open you should find there are two SCS entries in the Windows task bar - one for the Run Window and the other for the Editor Window. You can just switch back to the Run Window by clicking that task bar entry (or use Alt+Tab).
No, that's not it.
When I close th editor it does ask me if I want to save my changes. But if I click NO, then it removes the changes from the RUN window!
If I click YES, then the changes remain in the RUN window and are also written to the file.
I need to be able to close the editor whilst keeping the changes in the RUN window without writing them to the file.
Now, here's a funny thing. If I open the editor, make the change, and then click on the editor button AGAIN without closing the editor, the editor window moves back to the center of the screen and then if I close the editor the change is retained in the RUN window without me having to save!!
When I close th editor it does ask me if I want to save my changes. But if I click NO, then it removes the changes from the RUN window!
If I click YES, then the changes remain in the RUN window and are also written to the file.
I need to be able to close the editor whilst keeping the changes in the RUN window without writing them to the file.
Now, here's a funny thing. If I open the editor, make the change, and then click on the editor button AGAIN without closing the editor, the editor window moves back to the center of the screen and then if I close the editor the change is retained in the RUN window without me having to save!!
-
- Site Admin
- Posts: 3630
- Joined: Sun Jul 24, 2005 8:58 am
- Location: Brisbane, Queensland, Australia. TZ:GMT+10
- Contact:
OK, the program's doing what it's meant to except for one thing which I will fix in 9.2.5.
The Editor controls what is to be changed in the cue file, so when you 'close' the Editor the program asks you if you want to save the changes. If you say 'No' then the changes you have made are discarded and the cue data is rolled back to last saved state. If you say 'Yes' then the changes are written to the cue file.
What is incorrect in the processing is what happens when you click the Editor button a second time. The first time you click this button in a session, the Editor is started, which involves taking a snapshot of all the cues (so that SCS can roll back to that point if you want to discard changes); displaying the Editor window; and generally initializing the Editor.
If you switch back to the Run Window then the Editor is still active but the window is hidden. You can reveal the Editor Window (ie bring it to the front) by clicking on the Task Bar entry for the window, or by using Alt+Tab. If you click the Editor button on the Run Screen what SCS should do is just bring the Editor window to the front. BUT what currently happens is that the 'start Editor' processing is repeated.
The Editor currently has a button labelled 'Close Editor' and that activates the processing already discussed to either save or roll back changes. You can easily switch back to the Run Window without closing the Editor simply by clicking the Task Bar entry or (even easier) clicking the title bar of the Run Window (assuming it is currently visible behind the Editor Window). What I could also do is add another button to the Editor Window to switch back to the Run Window. All this button will do is bring the Run Window to the front, without asking about saving changes.
Note that in SCS 9, Editor operations are always immediately available in the Run window, so are always immediately available in the current session, whether or not you save them to disk.
The Editor controls what is to be changed in the cue file, so when you 'close' the Editor the program asks you if you want to save the changes. If you say 'No' then the changes you have made are discarded and the cue data is rolled back to last saved state. If you say 'Yes' then the changes are written to the cue file.
What is incorrect in the processing is what happens when you click the Editor button a second time. The first time you click this button in a session, the Editor is started, which involves taking a snapshot of all the cues (so that SCS can roll back to that point if you want to discard changes); displaying the Editor window; and generally initializing the Editor.
If you switch back to the Run Window then the Editor is still active but the window is hidden. You can reveal the Editor Window (ie bring it to the front) by clicking on the Task Bar entry for the window, or by using Alt+Tab. If you click the Editor button on the Run Screen what SCS should do is just bring the Editor window to the front. BUT what currently happens is that the 'start Editor' processing is repeated.
The Editor currently has a button labelled 'Close Editor' and that activates the processing already discussed to either save or roll back changes. You can easily switch back to the Run Window without closing the Editor simply by clicking the Task Bar entry or (even easier) clicking the title bar of the Run Window (assuming it is currently visible behind the Editor Window). What I could also do is add another button to the Editor Window to switch back to the Run Window. All this button will do is bring the Run Window to the front, without asking about saving changes.
Note that in SCS 9, Editor operations are always immediately available in the Run window, so are always immediately available in the current session, whether or not you save them to disk.
So what you are saying is that once the editor is open, it MUST STAY OPEN whilst the show is running, or I must save the changes to the cue file. Otherwise the changes are lost from the RUN window.
That is not intuitive and to me does not make sense. IMO should be possible to close the editor and retain the changes in the Run window without saving them to the cue file.
One way to do this might be to save to a temporary file associated with the session and run from that. Then when the session is closed, as th euser if he wants to keep the changes. This is what a number of audio editing applications do when you edit a .wav file during a session.
That is not intuitive and to me does not make sense. IMO should be possible to close the editor and retain the changes in the Run window without saving them to the cue file.
One way to do this might be to save to a temporary file associated with the session and run from that. Then when the session is closed, as th euser if he wants to keep the changes. This is what a number of audio editing applications do when you edit a .wav file during a session.