For change reporting style, the manual states that:
Code: Select all
0 - no event reporting
1 - down region events only
2 - Up region events only
3 - Down and up region events
9 - Down coordinate events only
10 - Up coordinate events only
11 - Down and up coordinate events
All other values reserved
I have a series of screens that the user goes between by swiping left or right. I have some buttons/touch regions on some of those screens. If I want to be able to register the touch in that region I can't register the swipe. If I register the coordinate events, I can't tell what button I have pressed.
My screens are identical at the bitmap level between the GTT and my displays (in fact, I'm positioning all of my elements on the GTT by referencing my GDI elements, so if I move something around in Visual Studio Designer, it shows up moved around on the GTT). So, I guess that I could just set up to register coordinate events, and then either fake the click at that coordinate on my application, or bounds test the coordinate against the buttons. So, I guess that it's not a huge issue for me, but is a much bigger pain than it should be.
If I hadn't decided to draw everything pixel for pixel in GDI as I was wanting it drawn on the GTT, I'd be in serious trouble, and I only did that because I can prototype a lot faster on GDI by working with the visual designer.
My solution would be to add the X and Y coordinates to the touch region report that's coming back. I would prefer that over a second reporting style that reported both coordinate and region events back, because without the coordinate given for the region, the user could only swipe the screens left or right on areas not covered by buttons, which would kind of be a pain.
Yea, this pretty much knocks me dead in the water. Some of my displays make use of the entire screen and I don't have room for a button to move the screens left or right, so I was doing it by swipe. But since that's not really possible, I can't navigate anywhere.