ssooo.. really didn't feel like doing any "work" this morning, so i decided to see if i couldnt' track down more info on the issue i've had with the MDI window "hanging"
wrote the following m-code
:CHANGERWAIT
TIME RESETMS
:TLOOP
TIME MS;\32
IF \32 < 2000 THEN GOTO :TLOOP
MESSAGE LOOP
\16= {\16+1}
IF \13 <> 20 THEN GOTO :CHANGERWAIT
---M15
opened an MDI window, and ran this. it did just what it was supposed to do, i was happy
then, i modified it by doing a macro call in the 1st line [LOGGING]
internals of the [LOGGING] macro are below
'THIS MACRO IS USED TO LOG VARIABLE CHANGES AND STATES.
'IT IS CALLED FROM WITHIN M143
LOGWRITE \9: LOGWRITE \11: LOGWRITE \300: \12=t: LOGWRITE \12: LOGWRITE \8: \13=s: LOGWRITE \13
now, using the MDI window to call M15, resulted in the window "hanging" and never actually getting to the mcode call! the top of the camsoft interface window says "please wait while is being verified", and this is as far as she'll go.
so, my guess is there is a conflict somewhere within the system in how a macro is called/used. even if there is, the system is far more capable than anything i could ever write, so i'm not trying to bash you guys, i just couldn't stand not having tracked the issue down.
if someone else could do this test, to verify that it's not just my control, that would be great, thanks!
-nate