Touch Issues

Archive
1

When I first started Pyxis 2 I realized that Touch collection stops working when you create a new AppDomain. I created a work around for it, but I thought I’d revisit the issue. Currently the only way I can handle touch collection over a new AppDomain is to run a thread in the background that polls the TouchCollectorConfiguration.GetLastTouchPoint. Obviously, I’d like to get rid of this resource wasting thread for the game system.

But these days searching “NETMF Touch AppDomain” brings up mostly Skewworks results. facepalm

Anyone been working on this?

2

I’m going to post here to leave breadcrumbs for others to follow:

I’ve walked through launching an application and aborted at different locations to see where the Touch Collection fails.

I can get all the way to creating the domain and instancing the object without any issues.

It seems the second a value is returned from the new domain to the default domain is when it locks.

Also it seems I can return a string from the object but once I try and work with a byte array it stops responding to touches. Even doing an Array.Copy is enough to make it fail.