Dear all,

I have a problem about dynamically activating touch driver.
I know there is one API called ActivateDevice(....) which could
activate drivers at runtime. But it seems only working on the
drivers which devices.exe drives. Now, the touch driver is drived
by GWES.exe. Its registry values were located at
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH.
Is there any way to load/activate touch driver at runtime ?
I got some situation needs to activate touch driver after GWES loads.

Hope someone could help me to solve this. Any comment is welcome.

Thanks in advance.

Regards,

Oliver Chang

Re: How to activate touch driver at runtime by Yannick

Yannick
Mon May 03 03:27:36 CDT 2004

This is not the final answer but... it might help you

On a pocketPC device, we used the following trick to deactivate the
touchscreen : we removed the calibration datas from the registry, so
touchscreen doesn't work any more. When we want to reactivate it, we just
reinsert the right calibration data.

If you have the source of your BSP, you can patch it to add an interface
that manage this activation/deactivation

--
----------------------------------------------------------------
Yannick Chamming's (eMVP)
ADESET
Windows Embedded Manager
ychammings AT adeset DOT com>
http://www.adeset.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------

"Oliver Chang" <jjchang@cs.nthu.edu.tw> a écrit dans le message de
news:dc8fedc3.0405022028.40f11766@posting.google.com...
> Dear all,
>
> I have a problem about dynamically activating touch driver.
> I know there is one API called ActivateDevice(....) which could
> activate drivers at runtime. But it seems only working on the
> drivers which devices.exe drives. Now, the touch driver is drived
> by GWES.exe. Its registry values were located at
> HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH.
> Is there any way to load/activate touch driver at runtime ?
> I got some situation needs to activate touch driver after GWES loads.
>
> Hope someone could help me to solve this. Any comment is welcome.
>
> Thanks in advance.
>
> Regards,
>
> Oliver Chang



Re: How to activate touch driver at runtime by Dean

Dean
Mon May 03 08:16:42 CDT 2004

GWES is the one that loads the touch driver, if gwes can't load it at init
time, it isn't ever going to load. What underlying problem are you actually
trying to solve?

--
Dean Ramsier - eMVP
Accelent Systems
http://www.accelent.com


"Oliver Chang" <jjchang@cs.nthu.edu.tw> wrote in message
news:dc8fedc3.0405022028.40f11766@posting.google.com...
> Dear all,
>
> I have a problem about dynamically activating touch driver.
> I know there is one API called ActivateDevice(....) which could
> activate drivers at runtime. But it seems only working on the
> drivers which devices.exe drives. Now, the touch driver is drived
> by GWES.exe. Its registry values were located at
> HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH.
> Is there any way to load/activate touch driver at runtime ?
> I got some situation needs to activate touch driver after GWES loads.
>
> Hope someone could help me to solve this. Any comment is welcome.
>
> Thanks in advance.
>
> Regards,
>
> Oliver Chang



Re: How to activate touch driver at runtime by jjchang

jjchang
Mon May 03 21:51:17 CDT 2004

Hmmm....

Thanks for all comments. Actually, my problem is just occurred in
our solution to touch driver. For some reason, we made the Fujitsu
Touch driver to be an installable module. We have a module wizard
that would set the related registry and copy the driver to \Windows
at WinCE boot-up. Everything is fine. After calibrating,
the calibration data could be saved at registry. So, the touch could
be ran well.
But when we load default settings of WinCE terminal, the calibration
data can't be kept any more.
We want to calibrate the touch first, and load default settings.
Finally, we want to give customers the products in default settings
and touch ran well too(after calibrating).

We could design an external way to save/restore the calibrated data.
But, we still need to activate touch by ourself.

By the way, our product is WBT type.

Regards,

Oliver

"Dean Ramsier" <dramsiernospam@accelentnospam.com> wrote in message news:<OG3RiDRMEHA.936@TK2MSFTNGP11.phx.gbl>...
> GWES is the one that loads the touch driver, if gwes can't load it at init
> time, it isn't ever going to load. What underlying problem are you actually
> trying to solve?
>
> --
> Dean Ramsier - eMVP
> Accelent Systems
> http://www.accelent.com
>
>
> "Oliver Chang" <jjchang@cs.nthu.edu.tw> wrote in message
> news:dc8fedc3.0405022028.40f11766@posting.google.com...
> > Dear all,
> >
> > I have a problem about dynamically activating touch driver.
> > I know there is one API called ActivateDevice(....) which could
> > activate drivers at runtime. But it seems only working on the
> > drivers which devices.exe drives. Now, the touch driver is drived
> > by GWES.exe. Its registry values were located at
> > HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH.
> > Is there any way to load/activate touch driver at runtime ?
> > I got some situation needs to activate touch driver after GWES loads.
> >
> > Hope someone could help me to solve this. Any comment is welcome.
> >
> > Thanks in advance.
> >
> > Regards,
> >
> > Oliver Chang

Re: How to activate touch driver at runtime by K

K
Tue May 04 22:51:05 CDT 2004

maybe you'll write a regular Stream Device Driver but not the native Touch
Panel Driver.
The Stream Driver can be laoded and unloaded at run-time, and you may use
mouse_event to inject the TouchPanel events is your driver's IST.

Most of the COM port interface Touch Panel Controller using this way.

But there will be some side effect if not ti use the Native Youch Panel, for
example Some of the Handwriting will get data directly from Touch Panel, and
so that if only using the mouse_event API the HWx App will not be
functional!!!

And the default Touch Panel Calibration UI will also can not be used!!


"Oliver Chang" <jjchang@cs.nthu.edu.tw>
???????:dc8fedc3.0405031851.13996bcb@posting.google.com...
> Hmmm....
>
> Thanks for all comments. Actually, my problem is just occurred in
> our solution to touch driver. For some reason, we made the Fujitsu
> Touch driver to be an installable module. We have a module wizard
> that would set the related registry and copy the driver to \Windows
> at WinCE boot-up. Everything is fine. After calibrating,
> the calibration data could be saved at registry. So, the touch could
> be ran well.
> But when we load default settings of WinCE terminal, the calibration
> data can't be kept any more.
> We want to calibrate the touch first, and load default settings.
> Finally, we want to give customers the products in default settings
> and touch ran well too(after calibrating).
>
> We could design an external way to save/restore the calibrated data.
> But, we still need to activate touch by ourself.
>
> By the way, our product is WBT type.
>
> Regards,
>
> Oliver
>
> "Dean Ramsier" <dramsiernospam@accelentnospam.com> wrote in message
news:<OG3RiDRMEHA.936@TK2MSFTNGP11.phx.gbl>...
> > GWES is the one that loads the touch driver, if gwes can't load it at
init
> > time, it isn't ever going to load. What underlying problem are you
actually
> > trying to solve?
> >
> > --
> > Dean Ramsier - eMVP
> > Accelent Systems
> > http://www.accelent.com
> >
> >
> > "Oliver Chang" <jjchang@cs.nthu.edu.tw> wrote in message
> > news:dc8fedc3.0405022028.40f11766@posting.google.com...
> > > Dear all,
> > >
> > > I have a problem about dynamically activating touch driver.
> > > I know there is one API called ActivateDevice(....) which could
> > > activate drivers at runtime. But it seems only working on the
> > > drivers which devices.exe drives. Now, the touch driver is drived
> > > by GWES.exe. Its registry values were located at
> > > HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH.
> > > Is there any way to load/activate touch driver at runtime ?
> > > I got some situation needs to activate touch driver after GWES loads.
> > >
> > > Hope someone could help me to solve this. Any comment is welcome.
> > >
> > > Thanks in advance.
> > >
> > > Regards,
> > >
> > > Oliver Chang