10-02-2011, 09:43 PM
Well, this Bible looks like it's still in Hebrew :?
I'm getting somewhere, but I'm getting frustration too.
-How to give the dialog set coordinates? I've been searching/trying, but all I can do is stretch the dialog or make it appear soemwhere not visible. I want to use 3 huge dialogs at the top of the screen - for MIDI Bank Select MSB, LSB, and Program change. I did discover DS_Center, but I can't define x y.
-How to trigger the code/run dialog - then populate with the triggering key (digit 1)? I'm presently using delays when converting MIDI to numeric to wait for the dialog to exist to send initial key but perhaps it can be simpler? I probably need the delay anyway to wait for the dialog to be enable. Do I need unique dialogs for each number?
-How to kill existing display before (re)opening another to prevent overlap? I'm using a font called LCD (11 segment calculator like). I didn't mention it but I've also got previous/next buttons to step throught the values, which can happen very rapidly. This is working, as the MIDI value is static [dialog(display -key 24- enter)] instead of dynamic [dialog(display -key 2- display -key 4- enter)]. When a program change occurs, the static value is converted into text, the dialog is opened, a delay, the text is inserted then enter. This works fine but the display looks "sluggish" as I have it set for a 2 second delay after IDOK. Killing existing dialog is actually necessary, as this MIDI translation method will open the dialog when Any Program Change is executed. I do realize I could use 2 dialogs, one dynamic and one static (dynamic IDOK no delay, static IDOK delay=(2) second). That way the dynamic would display numbers as typed, enter would immediately end that display, and instantly the static display would appear with the delayed close. Prv/Nxt would only trigger static display.
I Am learning something in all this... I realize you've given me bundles of info, I'm really in new territory and don't know how to understand a lot of it (yet).
My initial idea was to use OSD with Ctr+Alt+Win+(1-9 and 0), whcih wouldn't cause any active window confilicts. I wonder if that would simplify anything? In translating MIDI to QWERTY I try to avoid standard keystorkes, instead using special multikey keystrokes and letting QM send the standard key so I can have arguments, and to avoid any keystroke 'slipping through'. Either way, you've given me much essential info, It's just a slow process comprehending it all for my specific purposes... Many thanks.
I'm getting somewhere, but I'm getting frustration too.
-How to give the dialog set coordinates? I've been searching/trying, but all I can do is stretch the dialog or make it appear soemwhere not visible. I want to use 3 huge dialogs at the top of the screen - for MIDI Bank Select MSB, LSB, and Program change. I did discover DS_Center, but I can't define x y.
-How to trigger the code/run dialog - then populate with the triggering key (digit 1)? I'm presently using delays when converting MIDI to numeric to wait for the dialog to exist to send initial key but perhaps it can be simpler? I probably need the delay anyway to wait for the dialog to be enable. Do I need unique dialogs for each number?
-How to kill existing display before (re)opening another to prevent overlap? I'm using a font called LCD (11 segment calculator like). I didn't mention it but I've also got previous/next buttons to step throught the values, which can happen very rapidly. This is working, as the MIDI value is static [dialog(display -key 24- enter)] instead of dynamic [dialog(display -key 2- display -key 4- enter)]. When a program change occurs, the static value is converted into text, the dialog is opened, a delay, the text is inserted then enter. This works fine but the display looks "sluggish" as I have it set for a 2 second delay after IDOK. Killing existing dialog is actually necessary, as this MIDI translation method will open the dialog when Any Program Change is executed. I do realize I could use 2 dialogs, one dynamic and one static (dynamic IDOK no delay, static IDOK delay=(2) second). That way the dynamic would display numbers as typed, enter would immediately end that display, and instantly the static display would appear with the delayed close. Prv/Nxt would only trigger static display.
I Am learning something in all this... I realize you've given me bundles of info, I'm really in new territory and don't know how to understand a lot of it (yet).
My initial idea was to use OSD with Ctr+Alt+Win+(1-9 and 0), whcih wouldn't cause any active window confilicts. I wonder if that would simplify anything? In translating MIDI to QWERTY I try to avoid standard keystorkes, instead using special multikey keystrokes and letting QM send the standard key so I can have arguments, and to avoid any keystroke 'slipping through'. Either way, you've given me much essential info, It's just a slow process comprehending it all for my specific purposes... Many thanks.