Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 02 APR 1998 09:47:51AM Don Bakke wrote:

Hi Cameron. Didn't know if you saw this response from another thread…

Another thing you may want to consider depending on what you do in the timer event is to always kill it when you enter and then re-create it when you exit the event.

I'm not exactly sure what this would look like, however, it seems to be very similar to the method of setting the TIMER property to fire only once and the end of the TIMER event sets the TIMER property to fire only once again. It continues to do so (thereby creating a pseudo-TIMER loop) until certain conditions prevent it from re-setting itself.

Is this what you meant? If not, could you give me a skeleton of what you are talking about? If this is what you meant, then this doesn't help as this is the very schema that interferes with my CLICK events. As a side note, I managed to create an elaborate workaround with a TIMER that was set up to automatically repeat itself (the elaborate part dealt with killing the TIMER). Then after studying this solution even deeper I was able to eliminate the TIMER event all together! Nevertheless, it gave me a good education on using the TIMER event for other purposes but I would like to know why I can't kill the TIMER from within the TIMER event itself.

Thanks again,

dbakke@srpcs.com

SRP Computer Solutions


At 02 APR 1998 10:32AM Cameron Revelation wrote:

Don,

You were already doing basically what I was suggesting.

Cameron Purdy

info@revelation.com

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/8cf3c94b731a396e852565da004bcaef.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1