Some basic...

[MatsW]

I have looked around and searched but not found what I was looking for so here is a question:

- What is the macro for ALT Q and how should I do to get it sending it until I release the button on TB screen? (I keep the button down so to say).

Best regards
MatsW

[zorlac]

Hi MatsW, and welcome

- What is the macro for ALT Q and how should I do to get it sending it until I release the button on TB screen? (I keep the button down so to say).

Ther are two ways you could do it, depending on how you want the buttons to behave:

"hold" buttons will send one set of macros when you press them once (going into the held status), and another set of macros when you press them again (back to normal status).

or

"touch" buttons will send one set of macros when you press and hold the button down, and send another set of macros when you release the button.

So, hold buttons lock in the selected state, and touch buttons are momentary, and only stay in the selected state for as long as you hold the button down.

Whichever one you need, the macro options are defined the same way. If you are wanting keydown and keyup events, you will need "predef" macros.

Determine which button type you want, and add these macro defintions:

macro_select = predef:ALT, KEYDOWN
macro_select = predef:Q, KEYDOWN
macro_deselect = predef:Q, KEYUP
macro_deselect = predef: ALT, KEYUP

rawkey (obsolete now) and predef macros are briefly documented in the predef-and-rawkey-reference.html file in the docs directory. It contains a brief explaination of how to use predef and rawkey macros, along with a table that shows the valid rawkey/predef macro names. The select/deselect macros are covered in the how-to.txt file in the docs directory.

The docs are well overdue for an overhaul, and I am planning on re-doing them all while I am away at the start of September (linkable HTML how-to files)

[MatsW]

Sorry to say but it seems not to be working. Must have missed some settings somewhere.

I use the "touch" and it seems not to be sending any commands to the window (if you look at the small window line in the downer left). The other commands where I have used the "buttons", there is no problem at all and they are fully functional.

[zorlac]

paste the button config in here for the touch button, and i`ll take a look (button type "touch" was released in v1.0.1 wasnt it? Just going to check that, brain like a sieve... )

[zorlac]

oh and check your PMs on these forums!!

[MatsW]

You mean this?

[new-button]
name = _Raise
type = touch
tabname = TC (F7)
xpos = 591
ypos = 367
image_file = images\_Raise.GIF
macro_select = predef:ALT, KEYDOWN
macro_select = predef:Q, KEYDOWN
macro_deselect = predef:Q, KEYUP
macro_deselect = predef: ALT, KEYUP
[end-button]

[zorlac]

just trying this here... brb...

what version of TouchBuddy are you running? (Should say when you first start it up, in the titlebar or status bar of the initial window, before you load a profile).

[MatsW]

Sorry to say but again it was the human factor that caused the errors.
I just hade TB 1.0.0 instead of 1.0.1.
The TB Toolkit, however is 1.0.1 and I looked at that one when you asked.

After upgrading the TB, everything runs smoothly.

Thanks for all help
Mats

[zorlac]

cool Glad to hear that ("touch" buttons appeared in v1.0.1, hence why they were being ignored in your TB v1.0.0 install)