Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Changed behavior of 'Stop After Current' (Read 29029 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Changed behavior of 'Stop After Current'

Reply #25 –
Hi, long time no comment, but I saw the last year´s update and it is running nicely.

My issue is that I am desperately seeking for a method to avoid toggling this function. It would be great to switch the function into a defined "on" and "off" state, since you never know exactly how it is set, when using a remote control via girder or after hibernating the PC...

Any chance for quick implementation or ideas for a workaround, e. g. via command line?

KR
Holger

Re: Changed behavior of 'Stop After Current'

Reply #26 –
Was looking to solve exactly this problem and @Case delivered again.

Re: Changed behavior of 'Stop After Current'

Reply #27 –
Edit: clicking the topic and seeing the post above the last I thought it was the OP and was confused by the last post (since links now always go to the last post rather than the OP). Disregard.