10-10-2011, 07:44 PM
I'd hoped to come back with flying colors, but no so yet...
The (DTN_Show) functionality is great. Dynamic entry is working properly as requested with a one caveat - the Enter key doesn't end the input stage/reactivate previous window. That may ease the difficulty I'm having (re)allocating static entry which isn't coeexisting with dynamic now. I've been poking around attempting a fix with varied results. I think Enter ending input will help as a type of footer message - I'm deactivating the dialog effectively as below, but it seems Enter should have a more discreet action. Canceling the dialog returns to previously active window as expected.
Function KP_Close_KC_AL
Trigger CWq
The above method works well enough for dynamic entry, but my previous method for static entry is unreliable - after Enter new numbers are often appended to an existing dialog before it's timer closes. I'm dealing more with the triggering process now, which is nearly a different matter, but it should be the final stage.
Just to note, an MSB message will 'bang/display' LSB and PRG, and an LSB message will 'bang/display' PRG, which are static input functions. I also need to build a trigger to bang/display MSB LSB PRG to see all present values, all static mechanisms (but not exactly what I asked for originally.) I originally expected I'd be able to "easily" adapt code for all this, but I overestimated.
Below is an example of a digit trigger for reference. I'm open to any suggestion.
Function KP_1_KC_PRG_AL
Trigger CAW1
If you test the below attachment you'll see the difference between using the (Q) vs Enter then typing in new numbers.
The (DTN_Show) functionality is great. Dynamic entry is working properly as requested with a one caveat - the Enter key doesn't end the input stage/reactivate previous window. That may ease the difficulty I'm having (re)allocating static entry which isn't coeexisting with dynamic now. I've been poking around attempting a fix with varied results. I think Enter ending input will help as a type of footer message - I'm deactivating the dialog effectively as below, but it seems Enter should have a more discreet action. Canceling the dialog returns to previously active window as expected.
Function KP_Close_KC_AL
Trigger CWq

ifa(win("dialog_PRG_PRG" "#32770"))
,key Y
,act
,end
ifa(win("dialog_LSB_LSB" "#32770"))
,key Y
,act
,end
ifa(win("dialog_MSB_MSB" "#32770"))
,key Y
,act
,end
else end
The above method works well enough for dynamic entry, but my previous method for static entry is unreliable - after Enter new numbers are often appended to an existing dialog before it's timer closes. I'm dealing more with the triggering process now, which is nearly a different matter, but it should be the final stage.
Just to note, an MSB message will 'bang/display' LSB and PRG, and an LSB message will 'bang/display' PRG, which are static input functions. I also need to build a trigger to bang/display MSB LSB PRG to see all present values, all static mechanisms (but not exactly what I asked for originally.) I originally expected I'd be able to "easily" adapt code for all this, but I overestimated.
Below is an example of a digit trigger for reference. I'm open to any suggestion.
Function KP_1_KC_PRG_AL
Trigger CAW1

ifa-(win("dialog_PRG_PRG" "#32770"))
,PRG_Show "PRG" "1" 780 1 0x00FFFF 220
,end
ifa(win("dialog_PRG_PRG" "#32770"))
,key 1
,end
else end
If you test the below attachment you'll see the difference between using the (Q) vs Enter then typing in new numbers.