Wiki source for AgSetClip1
====agSetClip: can not nest agSetClip() in win32====
//This has been found to lead directly to this error on "clickthrough": [[AssertionFailed5 ***ASSERTION FAILED: aGDIWin.c:483 cp->theWindow!=NULL]].//
This error can occur while using automation. It is caused by a thread safety issue inside the PARIS application itself - there's a window of time in the app where a Windows screen re-draw can potentially "collide" with a thread of PARIS automation data, resulting in this "agSetClip" error. Even older single-CPU computers were theoretically vulnerable to it, but the chance of getting this error whenever you used automation was miniscule on single-core CPUs since the window of time in which it could happen was tiny. When multiple processor use was enabled by Mike's drivers, the chance of encountering this "window" increased - not just as simple direct multiples of probability but by a much greater factor. Now a heavy automation session has a better chance of triggering it than not.
Mike has included a workaround for this issue in a soon-to-be-released update of the PSCL; it drops the chance of encountering it back down to the original numbers (ie very unlikely), as well as containing a number of other tweaks, enhancements and updates. [[http://www.ensoniq.ca/ Contact Mike directly]] for an update if you encounter this error before he rolls out the update publicly.
----
Back to [[BugsTroubleshooting Bugs and Troubleshooting]]
//This has been found to lead directly to this error on "clickthrough": [[AssertionFailed5 ***ASSERTION FAILED: aGDIWin.c:483 cp->theWindow!=NULL]].//
This error can occur while using automation. It is caused by a thread safety issue inside the PARIS application itself - there's a window of time in the app where a Windows screen re-draw can potentially "collide" with a thread of PARIS automation data, resulting in this "agSetClip" error. Even older single-CPU computers were theoretically vulnerable to it, but the chance of getting this error whenever you used automation was miniscule on single-core CPUs since the window of time in which it could happen was tiny. When multiple processor use was enabled by Mike's drivers, the chance of encountering this "window" increased - not just as simple direct multiples of probability but by a much greater factor. Now a heavy automation session has a better chance of triggering it than not.
Mike has included a workaround for this issue in a soon-to-be-released update of the PSCL; it drops the chance of encountering it back down to the original numbers (ie very unlikely), as well as containing a number of other tweaks, enhancements and updates. [[http://www.ensoniq.ca/ Contact Mike directly]] for an update if you encounter this error before he rolls out the update publicly.
----
Back to [[BugsTroubleshooting Bugs and Troubleshooting]]
