Re: Closing a thread that is waiting for Irq
- From: "Steve Maillet \(eMVP\)" <nospam1@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 29 Jun 2005 06:32:41 -0700
Instead of a global flag you can use the little known Event Data functions
GetEventData and SetEventData to store the abort flag. This is preferred to
forcing the event closed as closing the event generates an error condition
and you can't distinguish it from a real error.
--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com
.
- Follow-Ups:
- Re: Closing a thread that is waiting for Irq
- From: Voidcoder
- Re: Closing a thread that is waiting for Irq
- References:
- Closing a thread that is waiting for Irq
- From: Igge H
- Re: Closing a thread that is waiting for Irq
- From: Anthony Pellerin
- Re: Closing a thread that is waiting for Irq
- From: Voidcoder
- Closing a thread that is waiting for Irq
- Prev by Date: Smartphone Platform?
- Next by Date: Re: Mapping physical memory into Application space
- Previous by thread: Re: Closing a thread that is waiting for Irq
- Next by thread: Re: Closing a thread that is waiting for Irq
- Index(es):