By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,412 Members | 929 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,412 IT Pros & Developers. It's quick & easy.

Prob with delay timer

P: n/a
My program takes in a key pressed value from the main routine and
based on the key pressed, it selects the command to be executed. The
problem I have is in creating a delay timer so that a message appears
on my screen for only one second. The condensed code is as follows:

#include <sys\timeb.h>
#define DELAY_1SEC 1000 // in millisec

void Scan_Menu_Keys(int key_press)
{ switch(key_press){
case 1: Execute1stCommand(); break;
case 2: Start_Timer();
while (!Timer_Expired(DELAY_1SEC))
strcpy(CG_ScreenKeyboard.Screen, "Display Message");
Clear_Screen();
break;
default: break;
}
}

void Start_Timer(){
ftime(&start_time); // ftime is function defined in sys\timeb
}

int Timer_Expired(){
ftime(&current_time);
time_diff = (int) (1000.0*(current_time.time - start_time.time) +
(current_time.millitm - start_time.millitm));
return (time_diff >= DELAY_1SEC);
}

The problem I ran into was that the timer would wait for one second
before displaying the message "Display Message". Effectively, that
meant the message never displayed because when it got out of the 1
second delay loop, the screen was cleared. I would love to get
suggestions on why this delay loop is not be executing the command
within the loop and any alternative methods to achieving the same
results.

Thanks in advance!

LYN
Jul 22 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a

"lynology" <ya*********@lmco.com> wrote in message
news:1b**************************@posting.google.c om...
My program takes in a key pressed value from the main routine and
based on the key pressed, it selects the command to be executed. The
problem I have is in creating a delay timer so that a message appears
on my screen for only one second. The condensed code is as follows:

#include <sys\timeb.h>
#define DELAY_1SEC 1000 // in millisec

void Scan_Menu_Keys(int key_press)
{ switch(key_press){
case 1: Execute1stCommand(); break;
case 2: Start_Timer();
while (!Timer_Expired(DELAY_1SEC))
strcpy(CG_ScreenKeyboard.Screen, "Display Message");
Clear_Screen();
break;
default: break;
}
}

void Start_Timer(){
ftime(&start_time); // ftime is function defined in sys\timeb
}

int Timer_Expired(){
ftime(&current_time);
time_diff = (int) (1000.0*(current_time.time - start_time.time) +
(current_time.millitm - start_time.millitm));
return (time_diff >= DELAY_1SEC);
}


Think about the above function. What happens if (say)

current_time.time = 1000000
current_time.millitm = 10

start_time.time = 999999
start_time.millitm = 100

I can't answer that question because you are using non-standard C++ (ftime),
but your method of working out the difference between two times may be
incorrect (I think it depends on whether millitm is a signed or unsigned).

john
Jul 22 '05 #2

P: n/a
lynology wrote:
The
problem I have is in creating a delay timer so that a message appears
on my screen for only one second.
case 2: Start_Timer();
while (!Timer_Expired(DELAY_1SEC))
strcpy(CG_ScreenKeyboard.Screen, "Display Message");
Clear_Screen();
Timer_Expired() is called with one argument. Whether this compiles,
depends on a previous declaration (which you `condensed out'). But
surely, it won't link with your definition below.
I would love to get
suggestions on why this delay loop is not be executing the command
within the loop
Presumimng, that the while-condition is true for exactly one second,
there will be many, many strcpy() executions in this time (depending on
your CPU speed). But I can't see a single _output_ statement. Is there
some hidden magic in writing to CG_ScreenKeyboard.Screen?
and any alternative methods to achieving the same
results.


Please consult the documentation of CG_ScreenKeyboard. This is not a
standard C++ class, so I'm afraid, that nobody here can help you.
Ralph

Jul 22 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.