Re: setTimer - what have I missed?
From: Bolla (trond.loekstad_at_no.abb.com)
Date: 02/25/05
- Next message: Paul G. Tobey [eMVP]: "Re: LCD Display"
- Previous message: turnsek: "PXA255 Suspend/Resume"
- In reply to: turnsek: "Re: setTimer - what have I missed?"
- Next in thread: Platform Builder: "Re: setTimer - what have I missed?"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 25 Feb 2005 16:31:12 +0100
Thanks a lot!
WaitForSingleObject with timeout 10ms is what I've used and that is what
it's gone be then!
/trond
"turnsek" <turnsek@discussions.microsoft.com> wrote in message
news:44D8F4CF-7294-41D7-B274-7C42A49ED790@microsoft.com...
> Hi!
>
> SetTimer routine is included in display based devices as part of the GWES
> functionality and is not so efficient as you might want, because it
requiers
> the whole message pump behind the thread. I used it on my LED notification
> thread under nleddrv and I found out that is very inefficient. I would
> suggest You to use Sleep or WaitForSingleObject and its timeout
capabilities.
> But that is only my opinion.
>
> Regards,
>
> Jernej Turnsek
>
> "Bolla" wrote:
>
> > Thanks for fast response!
> >
> > I have taken a serial based (UART) Modbus client application from
Windows PC
> > environment and ported it to my WinCE Xscale 255 hardware platform based
on
> > the Lubbock (XSC1BD) BSP. There is no display on my board.
> > In my BSP I have included the feature "Minimal GWES Configuration" in my
> > build, but still the method SetTimer is not available.
> >
> > I have come around the problem by making my own timer thread, but would
like
> > to use the system call SetTimer instead (guess it is more efficient).
> >
> > Do you know which GWES feature(s) that is required, and can I use it for
my
> > Headless device?
> >
> > /trond
> >
> > "Bruce Eitman (eMVP)" <beitmannospam@NOSPAM_applieddata.NOSPAM_net>
wrote in
> > message news:u3imFH0GFHA.3612@TK2MSFTNGP09.phx.gbl...
> > > A quick look in winuser.h would give you the answer. It is dependent
on
> > > GWES_TIMER. Since you have a headless system, which I take to be a
system
> > > without GWES, then no your platform would not support it.
> > >
> > > This makes sense, since SetTimer drives an event, and you don't have
an
> > > event sub-system in your platform.
> > >
> > > What are you trying to do, maybe there is a way.
> > >
> > > --
> > > Bruce Eitman (eMVP)
> > > Senior Engineer
> > > beitman AT applieddata DOT net
> > >
> > > Applied Data Systems
> > > www.applieddata.net
> > > An ISO 9001:2000 Registered Company
> > > Microsoft WEP Gold-level Member
> > >
> > >
> > > "Bolla" <trond.loekstad@no.abb.com> wrote in message
> > > news:%23YrcAZxGFHA.3628@TK2MSFTNGP15.phx.gbl...
> > > > I wished it was so, but I used SetTimer in my code.
> > > > Can it have anything to do with my tiny headless device platform
> > > > configuration?
> > > > I thought this was part of the kernel anyway!
> > > > Looking forward for any ideas?
> > > > /trond
> > > >
> > > > "Zhongwei Wang" <wang@applieddata[dot]_net> wrote in message
> > > > news:evtwntrGFHA.3156@TK2MSFTNGP10.phx.gbl...
> > > > > Looks like you typed SetTimer as setTimer.
> > > > >
> > > > > --
> > > > > Zhongwei Wang
> > > > > Applied Data Systems
> > > > > www.applieddata.net
> > > > > Application - Ready embedded systems
> > > > > Microsoft Windows Embedded Partner
> > > > > Gold Level Member
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >
- Next message: Paul G. Tobey [eMVP]: "Re: LCD Display"
- Previous message: turnsek: "PXA255 Suspend/Resume"
- In reply to: turnsek: "Re: setTimer - what have I missed?"
- Next in thread: Platform Builder: "Re: setTimer - what have I missed?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
