| Description: | If kernel property ScDebug() is set to scComDebugNoOutput, there could occur problems before:
The mode scComDebugNoOutput means, that there is no message box arising, but an event is sent instead.
Because the event is sent in the thread context, where the error message occurred, the error messages can even occur NOT under main thread.
In case error message in scComDebugNoOutput mode, the event was 'fired' through the standard ScUpdate event, which may have caused problems, when jumping to all the update handlers NOT under main thread context ( main thread context is the thread which loaded SAM ).
Instead now, a new event is created, only for this 'DebugNoOutput' purpose - the new ScDebugModeNoOutput event instead of the ScDoUpdate event before - with additional advantage, that the error message string also is sent within the new event ...
So WITHOUT changes in customer SAM host software ( ClientCtrl is not concerned by this ), but using new SAM version, the ScDebugModeNoOutput event will no more occur at the custom SAM host app. |
