Touch type button doesn't work for Wheel Brakes (w key)

[Wild.Bill.Kelso]

I have a touch type button with 2 images. The macros looks like this:

macro = w

Pretty simple. But when taxing in the A10, the TB touch button does not stop the plane from taxing. But when I press the w key myself, it does slow down and stop like normal.

[Wild.Bill.Kelso]

Ooops! I didn't read all the docs. I assumed that a touch button just send a keystroke when it was touched. But as I just read the docs, it says the touch button is like the hold button, and uses the macro_select and macro_deselect. My bad. Going to give it another try right now...

I am also working getting the buttons that start my engines to work. Even with the keyboard, I've always found that I have to press 'and hold' the Shift-Home key to start the right engine. I don't know why I have to hold it. But I wanted to use the new Hold/no_reset button to start and stop each engine. Now I'm not sure if that will work. I'm trying to use the touch button so I can actually have the keystrokes 'held down' to see if that works.

Does anybody else have this problem where you have to hold the keys down to start the engines?

[zorlac]

just stick a {PAUSE xxx} macro in there, between the key down events and the key up events (where xxx is the number of milliseconds to delay)

[Wild.Bill.Kelso]

Since I now found out that a Touch type button has a macro_select and macro_deselect, it makes me wonder...

When you press and hold the Touch button, does it act like when you press and 'hold' a keyboard button down? Does it keep sending that macro until you release it. Or does it just send the macro_select keystrokes once and wait.... (not sending anything)... for you to release the button, then send the macro_deselect?

[Wild.Bill.Kelso]

PS: I've been testing my A10 profile all day, and have gotten several TB CTDs when I close TB. Also, have had that dredded "ERROR: More than one window found to send xxxxxxxxxxx". I was thinking, can you just send the keystrokes to both windows? Sounds stupid, but I wonder how it would work...

[zorlac]

Originally Posted by Wild.Bill.Kelso

Since I now found out that a Touch type button has a macro_select and macro_deselect, it makes me wonder...

When you press and hold the Touch button, does it act like when you press and 'hold' a keyboard button down? Does it keep sending that macro until you release it. Or does it just send the macro_select keystrokes once and wait.... (not sending anything)... for you to release the button, then send the macro_deselect?

select macro sent once on press, deselect macro sent once on release

[zorlac]

Originally Posted by Wild.Bill.Kelso

PS: I've been testing my A10 profile all day, and have gotten several TB CTDs when I close TB. Also, have had that dredded "ERROR: More than one window found to send xxxxxxxxxxx". I was thinking, can you just send the keystrokes to both windows? Sounds stupid, but I wonder how it would work...

I`ll see what I can do... i wish I could find this bug

[Wild.Bill.Kelso]

I was just getting that error again, so while Lockon was running I opend Process Explorer. One thing I did notice was that when I did a search for LOCK ON, I returned a bunch of stuff, but they were all either of type Handle or DLL Substring. Probably not it, but it was the only thing I noticed that had 2 types for Lockon.

I also noticed that the error seemed to start when I was touching buttons on the touchscreen, then if I touched just one button on the keyboard and went back to touch the touchscreen, the error started. I think I saw this happed about 3-4 times this afternoon. Even after I rebooted I think.

Gotta reboot now, can't get rid of the 'more than one window to send' but...

[zorlac]

I really wish I could drop the "sendto" options, its a legacy thing from before I knew what I was doing

The sendto options only really make sense now for GUI based applications, so you can swap between active windows. The "sendto" option makes the send_macro routine look for the window name, *makes it active or got focus*, and then sends the keys. Great for GUI apps on your desktop, but a bit useless for games to be honest.

To be honest, while playing a game, there is no need to be using the sendto option. TB will just send the macros blindly, and if the game is active, then it will receive the macros.

I would highly recommend that you drop the sendto options in any profile (for games) and just let TB send the keypresses.

[Wild.Bill.Kelso]

I remember now some post about leaving Send To blank for the Options and Buttons. Maybe just put a section in your how-to.txt file for Error Messages and possible solutions. Or maybe a new Error Messages.html?

I totally agree that the send to is not needed since the game is the main app (with the focus) when you are playing it. And that's all you care about, is when you are playing the game, it has the focus, so it WILL receive any keystrokes from anywhere. That's how I have always coded my SendKey apps.