I need to suppress this warning

Jack S wrote on 4/11/2024, 6:10 AM

@jetdv Edward, I wonder if you can help me with this one. I have a batch render tool and I need to be able to abort the render sequence. This tool is in my Application Extension, so when the render sequence starts the UI is locked against any button action. I have a few lines of code that checks the render status for Cancel. If true it flags the render sequence to either abort the whole sequence or just aborts the one in progress when the cancel button is clicked, depending on whether a message box I provide has the response Yes or No. My problem is that when the Cancel button is clicked, another system message is displayed as below:-

This somehow prevents the abort flag from being set. If I manage to respond to this dialog before the current render completes, my message box appears which allows the abort sequence process to complete. It's as if the RenderStatus.Canceled state is cleared after the current render is completed and before I can test for it so that the abort mechanism isn't initiated. Do you know of a way to suppress this dialog? I've scoured the API and can't see an obvious boolean. Thanks for any help you can give me.

Comments

jetdv wrote on 4/13/2024, 8:13 AM

I've always just let VEGAS handle any cancelling of renders and just check to see if the render completed successfully popping up a message if it was cancelled.

Jack S wrote on 4/13/2024, 10:06 AM

@jetdv Thanks for responding. My problem is this. I have some code that checks the RenderStatus for Cancel. If it is, I display a message box giving the option to abort the render sequence. The render sequence is an array of projects to be rendered. If the 2nd dialog (shown in my post) isn't responded to before the current render finishes, the next project in the sequence loads and starts to render. The problem then re-occurs.
Since asking you the question, I've realised that the problem occurred because I was testing the tool with quite short projects (for obvious reasons). Under normal circumstances, projects will be long enough to allow plenty of time for the user to respond to the second message, allowing my message box to show, thus pausing the render sequence until a response is given.
Thanks again for your time. I realise that the messages are system created and therefore untouchable.