What a pain this has been to work on, especially without a proper touch device to test with. I managed to get my hands on a Surface Pro 3 to use while working on the touch aspects RadialMenu and the toolbar. Astounding that even in windows 8 there is no -default- capability to handle mouse/touch/pen input all at the same time and we have to use workarounds.
The first problem is the fact that when a pen device gets in range touch input is completely ignored as if it's been turned off. The only way to allow both is to read the raw input of the touch hardware and handle it completely on your own, this means keeping track of touch down/touch up/touch hold, coordinates of the touch, number of touches and which control has focus.
Windows by default promotes touch and pen events to normal mouse events to support older applications that don't have built in support for pen and touch. This means that even though I may have processed the raw touch data and handled it, windows has no way of knowing. For normal mouse events you can let the system know that it's been handled and it should ignore the event when it sees it, not so for touch/pen.
I had hoped with Windows 8 we wouldn't be forced to read raw input data to get pen button states and/or support more then one input method at a time, but.. whatever.
Simultaneous pen + touch is the last feature I wanted to implement before doing a feature freeze and concentrating on bugs and performance. Over the next coulple days I'll be testing RadialMenu on the surface and my LE1700 and preparing a more stable release. After that there will be no new big features added until RadialMenu is more stable and error checking is more robust. I'm fairly displeased with the memory footprint of RadialMenu as well as the startup speed. I don't know about anyone else, but the startup speed of RadialMenu is much faster on my Motion Computing LE1700 and LE1600 then it is on the Surface 3. I've also found a quite a few issues I wasn't aware of with RadialMenu on the Surface 3 that need to be fixed.
-incrediclint
The first problem is the fact that when a pen device gets in range touch input is completely ignored as if it's been turned off. The only way to allow both is to read the raw input of the touch hardware and handle it completely on your own, this means keeping track of touch down/touch up/touch hold, coordinates of the touch, number of touches and which control has focus.
Windows by default promotes touch and pen events to normal mouse events to support older applications that don't have built in support for pen and touch. This means that even though I may have processed the raw touch data and handled it, windows has no way of knowing. For normal mouse events you can let the system know that it's been handled and it should ignore the event when it sees it, not so for touch/pen.
I had hoped with Windows 8 we wouldn't be forced to read raw input data to get pen button states and/or support more then one input method at a time, but.. whatever.
Simultaneous pen + touch is the last feature I wanted to implement before doing a feature freeze and concentrating on bugs and performance. Over the next coulple days I'll be testing RadialMenu on the surface and my LE1700 and preparing a more stable release. After that there will be no new big features added until RadialMenu is more stable and error checking is more robust. I'm fairly displeased with the memory footprint of RadialMenu as well as the startup speed. I don't know about anyone else, but the startup speed of RadialMenu is much faster on my Motion Computing LE1700 and LE1600 then it is on the Surface 3. I've also found a quite a few issues I wasn't aware of with RadialMenu on the Surface 3 that need to be fixed.
-incrediclint