Capturing input from USB peripheral

[stupomer]

Hi Gintaras,
I am trying to assign the buttons on a Phillips SpeechMike to triggers for custom QM macros. Problem is that there is no way to assign them to specific keystrokes. When I turn on the Acc log, I get nonspecific stuff like this when I press the buttons in the app I am using:

1815. REORDER, WINDOW, 0
ow: class="WindowsForms10.Window.0.app.0.33c0d9d", text="TimerNativeWindow"
ao: role=WINDOW, state=0x148000, name="TimerNativeWindow"
1816. CREATE, WINDOW, 0
ow: class="WindowsForms10.Window.0.app.0.33c0d9d", text="TimerNativeWindow"
ao: role=WINDOW, state=0x148000, name="TimerNativeWindow"
1817. DESTROY, WINDOW, 0
ow: class="WindowsForms10.Window.0.app.0.33c0d9d", text="TimerNativeWindow"
ao: role=WINDOW, state=0x148000, name="TimerNativeWindow"

Is there any way to "spy" on the input from the peripheral more directly and then create a trigger from that information?

Thanks, Stuart

[Gintaras]

What these buttons do normally? If they don't send keys or mouse or something than can be used for a QM trigger, then I don't know.

[Gintaras]

Maybe they send some messages to the active window. Test with this dialog.
Function Dialog85

Code:

Copy      Help

\Dialog_Editor
function# hDlg message wParam lParam
if(hDlg) goto messages

out
if(!ShowDialog("Dialog85" &Dialog85)) ret

;BEGIN DIALOG
;0 "" 0x90C80AC8 0x0 0 0 223 135 "Dialog"
;END DIALOG
;DIALOG EDITOR: "" 0x2030109 "*" "" ""

ret
;messages
OutWinMsg message wParam lParam
sel message
,case WM_INITDIALOG
,case WM_DESTROY
,case WM_COMMAND goto messages2
ret
;messages2
sel wParam
,case IDOK
,case IDCANCEL
ret 1