Here is what I have:  an MFC dialog based application.  There is a main
dialog, with a date/time picker control, an OK button and a Cancel
button.  The date time picker control is hooked to a CTime object
m_CurrentTime in the dialog class. The date/time picker is set to "time"
format, and is user editable. There is also a SYSTEMTIME object, st,
defined as a dialog class member.

The dialog constructor assigns the current time to m_CurrentTime as
follows:

m_CurrentTime = CTime::GetCurrentTime();

this part seems to work OK. When the applet starts, the current system
time is displayed in the date/timer picker.

Then, in the OnOK function, I do this, to supposedly set the system time
to the time in CurrentTime.

m_CurrentTime.GetAsSystemTime( st );
::SetSystemTime( &st );

This program is built using VC++ 6.0, SP3, on Windows 95.  When I
execute it, and set a new time and click OK, the following happens:

The system clock seems to get updated, but it takes 5 to 10 seconds
after the program closes, before the taskbar clock shows the updated
time, which is inevitably something different from what I select in the
date/time picker.  Also, after running this program, my system date is
now wrong.

Can anybody give me any clue on what exactly I am doing wrong?  Thanks
in advance!

Phil

--
remove "REMOVE-NOSPAM" from my e-mail address to reply.

Is this just a windows quirk, that it takes the actual displayed clock
several seconds to sync with the time that has been set, or is this a result
of some problem in my program?  I tend to think it's my program, because
when I set the time using the standard windows date/time applet, the clock
updates as soon as I click "apply."

Any ideas / suggestions / thoughts would be greatly appreciated.

Phil

--
remove "REMOVE-NOSPAM" from my e-mail address to reply.

With best wishes,
    Igor Tandetnik

Definitely implement broadcast and handling of WM_TIMECHANGE message, as Igor
Tandetnik suggested.  EXCEPT, do not broadcast the message when the user is
running Windows 2000.

--
remove "REMOVE-NOSPAM" from my e-mail address to reply.

Phil

--
remove "REMOVE-NOSPAM" from my e-mail address to reply.

m_CurrentTime.GetAsSystemTime( st );
::SetSystemTime( &st );
::SendMessage( HWND_TOPMOST, WM_TIMECHANGE, 0, 0 );

now the clock updates immediately, as it should.   But, I'm still getting the
WRONG time! Ugh...  Is there any conversion involved in any of these time
functions, that I'm not accounting for? I see that SetSystemTime expects the time
in UTC.  Is that a factor? Am I getting the time expressed in my local time zone
earlier in the program, and need to convert to UTC before calling SetSystemTime()?

Or am I overlooking something else?  Thanks again for the help!

Phil

--
remove "REMOVE-NOSPAM" from my e-mail address to reply.

Ok, I changed my OnOK() to this:

m_CurrentTime.GetAsSystemTime( st );
::SetSystemTime( &st );
::SendMessage( HWND_TOPMOST, WM_TIMECHANGE, 0, 0 );

now the clock updates immediately, as it should.   But, I'm still getting
the
WRONG time! Ugh...  Is there any conversion involved in any of these time
functions, that I'm not accounting for? I see that SetSystemTime expects the
time
in UTC.  Is that a factor? Am I getting the time expressed in my local time
zone
earlier in the program, and need to convert to UTC before calling
SetSystemTime()?

Or am I overlooking something else?  Thanks again for the help!

Phil
--------
remove "REMOVE-NOSPAM" from my e-mail address to reply.

Phil

--
remove "REMOVE-NOSPAM" from my e-mail address to reply.

Try SetLocalTime instead

With best wishes,
    Igor Tandetnik