Jim,
Thanks for all that information!!!!
Your comments about timer interval and file sizes make me feel much more confident.
Thanks for taking your time to tell me this stuff....
As for the ListSetup coding. I hesitate to put that into the timer.fil because I want to keep that file small so I try not to put code into it when I can find another way. What I did not tell you is that there are 14 different versions of that code. Each version is for a specific process on my machine. That code was created for the purpose of letting a user click on a screen graphic that represents one of the 14 different processes on my machine.
The user clicks on the graphic button, that listsetup menu pops up, and the user can monitor all the current process parameters and see them changing for that particular part of the process.
Now dont blame me because you created this question!! LOL
Question / Comment: I understand that I could make it so that when a user clicks on one of the graphics, an Mcode changes a variable, (lets say \50 ). I could then put code in the timer.fil to check that \50.
IF \50=1 THEN Run this listsetup code.
IF \50=2 THEN Run this listsetup code.
But what I dont understand about filling up the timer.fil (and you hit on this) is will things bog down even though IF \50=?? THEN never holds true??
What you said leads me to believe I can fill that timer.fil up with lots of stuff so long as an IF THEN statement is used to see if it needs to be run..
In English: No matter how much code is in the timer.fil , if the code doesnt run, it wont slow anything down.
Would that be a correct statement?
Thanks a bunch for your help Jim,
Murphy  |