CE5 中的触摸屏阻止来自外设的数据流量
我们正在.Net CF 2 C# 中开发一个带有Windows CE 5（很快将升级到6）的平台。
我们最近发现，如果我们在使用外设时触摸触摸屏，外设数据流量就会超时，我们的应用程序就会崩溃。所以看起来触摸屏挡住了它。作为快速修复，我们希望在使用外围设备时禁用触摸屏，然后重新启用它。
所以我们的问题是，我们该怎么做？
我们在操作系统构建中是否需要一些额外的软件包，或者我们可以手动完成。我们已经了解了 touchpaneldisable() 和 touchpanelenable(...)。但enable方法需要回调函数的句柄。所以我不知道如何解决这个问题。
We are developing a platform with Windows CE 5 (soon to be upgraded to 6) in .Net CF 2 C#.
What we have recently discovered is that if we are touching the touchscreen while using our peripheral, the peripheral data trafic times out and our application crashes. So it seems like the touchscreen is blocking it. As a quick fix we would like to disable the touchscreen while using the peripheral, and the reenabling it.
So our question is, how do we do it?
Do we need some extra packages in the OS build or can we do it manually. We have had a look at touchpaneldisable() and touchpanelenable(...). But the enable method requires a handle to the callback function. So I have no idea on how to fix this.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
从应用程序的角度来看，这确实不是解决办法。触摸屏驱动程序与其他驱动程序略有不同，因为它们由 GWES 加载（并进入），而不是 device.exe。它们并未设计为禁用和启用，尽管一些 OEM 确实提供了该功能（通常只是屏蔽触摸屏中断）。
听起来触摸屏采样率非常高，并且设备在开始采样时使处理器饱和。 OEM 可能需要解决这个问题。某些 OEM 确实提供注册表项来调整驱动程序行为，因此请与他们联系以了解您是否可以使用该注册表项。在这种情况下，您也许可以自己解决问题。
From an application perspective tehre really isn't a fix. Touchpanel ddrivers a re alittle different than otehrs becasue they get loaded by (and into) GWES, rather than device.exe. They are not designed to be disabled and enabled, though some OEMs do provide the capability (typically by just masking the touch panel interrupt).
It sounds like the touchpanel sampling rate is really high and the device is saturating the processor when it startes sampling. It's something that the OEM probably needs to fix. Some OEMs do provide registry entries to adjust the driver behavior, so check with them to see if this might be available to you. In that case you may be able to fix the issue yourself.
如果您有 BSP，您可能需要查看 此博客文章，因为它提出了触摸驱动程序可能存在的瓶颈。
If you have the BSP you might want to go through this blog post as it suggest possible bottle necks for the touch driver.