sensor movement

[eagledeer]

Hi:

When I turn (e.g.) optics on in the su25, pressing a button on the touch screen will also cause the shkval to jump to that point as movement is mapped to mouse. I seem to remember there may be some way to avoid this? Or is it something to try and work around?

Thanks

P.S. using viper's profile for cougar and exeter's updated for FC2

[Scrambler]

Hi

Not certain I fully understand what the problem is but have you tried changing the mouse options in the TB cfg file


e.g. this section

#=====================
# In Local mode, when you press on the TouchBuddy window, the mouse/cursor
# will move to the area of the button, but after pressing the button, the
# cursor will stay there. By defining the following value, TouchBuddy will
# move the mouse/cursor to the defined position after a button press.
# If its defined as "centre", the mouse/cursor will be moved to the centre
# of the currently active window.
# If its defined as "previous", the mouse-cursor will be moved to where
# TouchBuddy saw it last time round its 1 second timer loop (this option works
# remarkably well from my limited testing!)
#mouse_position_after_press = 320,240
# or
#mouse_position_after_press = centre
# or
#mouse_position_after_press = previous

Try the mouse_position_after_press = previous to see if that makes any difference in the behavior.

[eagledeer]

Thanks Scrambler. Will try when I get home, but I believe that'll do it!