ok, so the sequence of events are not guaranteed... I also noted that if event A is triggered before event B then there is nothing that guarantees that the handler of event A will not get interrupted by event B.
Is there some way that I can ensure that all the of the code that handles event A is executed before event B is alowed to be triggered. I mean some way to maybe pause the reporting of events until the handler code of A has executed, or some way to mark the handler code of event A to be non-interruptible by events? On 12 Feb, 15:27, Mike Fry <[email protected]> wrote: > On 2011/02/12 16:02, Marcus wrote: > > > Yes I am using SystemEvents.PowerModeChanged (and also > > Win32_PowerManagementEvent), it seems like the TimeChanged event > > triggers first though. But anyway...I should be able to use these > > together to solve my problem. > > > It is just one thing ... can I be sure the sequence of events is > > allways the same? > > Get real! This is Microsoft! > > -- > Regards, > Mike Fry > Johannesburg
