1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

WAD DELAY doesn't always

Discussion in 'Support' started by Steve Fabian, Mar 21, 2012.

  1. Steve Fabian

    Joined:
    May 20, 2008
    Messages:
    3,523
    Likes Received:
    4
    Some time ago there was a thread regarding DELAY - it was reported, IIRC by Vince, that issuing the DELAY command does not always delay execution of the next command. I am still struggling with it in 13.04.54 on WinXP SP3 platforms (32b). My code uses a DELAY 5 after detecting an event to allow the user 5s to choose an action; ofter the delay does not take place.
     
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,726
    Likes Received:
    80
    Not reproducible here.

    Do you have a reproducible failcase?
     
  3. Steve Fabian

    Joined:
    May 20, 2008
    Messages:
    3,523
    Likes Received:
    4
    Sorry, complaint withdrawn. My problem is a timing issue - at what point in a fast loop another process creates a message window. If the new window is first detected during the 1ms when the 200-ms loop is just cycling, it skips the delay. My own bad design! It is like trying to determine current date and time by looking at %_date just before midnight, but at %_time at or after midnight.
     

Share This Page