A couple of wild ideas

[Wild.Bill.Kelso]

Fingers are crossed, and prayers have been submitted for His approval.

[AndyHill]

Originally Posted by zorlac

SetCapture will block all attempts to move the mouse from any drivers too The drivers report to the system, and the system is enforcing the lock to the area

I`ll see if I can contact Oleg via whatever channel...

But what if the drivers won't use the mouse in any way? There has to be a direct way to get info from and to the touchscreen, at some point the driver must see raw position values, which it then translates into mouse movement. If there was a way to get to this raw data you wouldn't have to worry about mouse issues ever again. It would probably be beneficial for touchscreen manufacturers to allow simple and direct access that could be used regardless of any properties of other software running simultaneously.

[zorlac]

the touchscreen drivers see you press the screen, they work out what x/y position that is on the windows screen.... then the only way to get the button on the touchscreen pressed is to tell the system to move the mouse to that x/y position and then tell the system to send a mouse click.

The touchscreen drivers know where the x/y position is, but without hitting the system at a hardware level (very hard, and probably impossible without M$ signed drivers in Vista), the only way to get the mouse to move is to do a system call to move it there. If the system has a ClipCursor or SetCapture lock, then it doesnt matter that the touchscreen drivers are trying to move the mouse to that position, the system will stop the mouse when it reaches the border of any locked area.

If I can bypass SetCapture, all this becomes an obsolete conversation anyway

[AndyHill]

Hmm yes, of course, that's where the problem lies. I don't know if it would be impossible or just too much work to hard code the button positions in the profiles, but I don't have to tell you how much it would mean to have guaranteed and simple local mode compatibility for every game out there. Hmm now that I think of it things like scrollbars would make direct position calculation quite difficult indeed. I kind of think touchscreen manufacturers would be in best position to fix teh problem. At least it might be worth a shot contacting them and telling them what you're doing. Anyway, it would be fair to warn them before they run out of stock since everyone is going to want their own touch-buddies soon.

[Vegas]

Originally Posted by zorlac

If I can bypass SetCapture, all this becomes an obsolete conversation anyway

I'm voting for "bypass surgery"!!! Go Zorlac!

[zorlac]

Rushed home, fired up TB and... ReleaseCapture doesnt work with iL-2 bugger....

[zorlac]

I think its using a DirectX call... maybe...

http://www.gamedev.net/reference/art...rticle1657.asp

[Urban]

its ok Client/Server ftw

[AndyHill]

Noooooooo getting TB to work in any game in local mode would be a huge deal for most. People willing to mess with two computers are a minority within a niche when it comes to flightsimmers and in other genres there won't be that many.

[zorlac]

Its down to how the game "locks" the mouse. If it uses a system call that I can undo, then its probably going to work, but if they are calling DX calls, then it probably wont work in local.

As for the touchscreen drivers, I`ll say this once again.... if the system has locked the mouse to an area, then it doesnt matter what the drivers do. All they do is tell the system that they would like to move the mouse to a specific location. If the system is blocking or restricting that movement, it doesnt matter what the drivers try to do, it just wont work. The system controls everything... if it doesnt want to allow you to do something, it wont, no mmatter if its an end user program or a system driver.