Xdialog, trapping Enter Key

[Jim Chapman]

Hello,

I hope someone puts me out of my misery. I am trying to trap the Enter keystroke in a Xdialog box. Below is the code:

DIM SHARED vWeekly as C
DIM SHARED vDay1 as C
DIM SHARED vDay2 as C
DIM SHARED vDay3 as C
DIM SHARED vDay4 as C
DIM SHARED vDay5 as C
DIM SHARED vDay6 as C
DIM SHARED vDay7 as C
DIM SHARED varC_result as C
ok_button_label = "&OK"
cancel_button_label = "&Cancel"
varC_result = ui_dlg_box("Enter New Dosage Info",
{endregion};
%dlg%,

[Jim Chapman]

RE: Xdialog, trapping Enter Key

I think I figured out why I can get both results, apparently the Xdialog box is 'firing' twice, so I will either get the "OK" or the "enter" return on one of the two 'firings'. Can anyone see anything in this code that would cause this?

Thanks,
Jim

[Jim Chapman]

RE: Xdialog, trapping Enter Key

To All Xdialog enthusiasts,

I doubt any of you can duplicate my problem, but I figured it out, or maybe I should say it is working now. Here�s is what I discovered. I created the Xdialog box with the genie. Alpha generated it�s standard code with an OK button as default and an OK event and a Cancel event defined for the buttons.

I then took the generated code and simply added {on_key=enter}, and a simple if�then statement to test for the enter key and set a_dlg_button = ��. It did not work. Hitting the enter key would close the Xdialog box. I could not trap the enter key. I played with this for quite a while and posted my first message. I continued playing with this, removing all ui_msg_box() and debug() commands as I felt that I was muddling up the focus (the old �watcher changes the outcome of the experiment simply by watching� routine). I place counters in the Xdialog code and discovered that for each press of the enter key, Alpha was cycling twice through the code, even though I was sending the a_dlg_button = �� command. I then embedded variables in the code and set them to the value of a_dlg_button, and read these variables after the xdialog box closed. I found that the first time through the code, a_dlg_button was indeed set to �enter�, but the second time through the code a_dlg_button was set to �OK�. I could see no reason for this, but began looking for another event that could possibly be firing. I removed the event code from the OK button. This caused Alpha to only cycle once through the code, but the xdialog box still closed after an enter press even though a_dlg_button was set to ��. I then removed the default asterisk (*) from the OK button. That did it, the Xdialog box began working as I would expect. The enter key was trapped and I could control what happened. However, I put back in the asterisk, and the event code in the buttons expecting that the problem would crop back up. It didn�t, all works as expected, with the identical code I started with.

However, I went to my original post and copied the code, pasting it back into A5 and it does error out. But removing the astrisk solves the problem. For any of you who are still with me, you can try the following to demonstrate what I am talking about.

Thanks,
Jim

DIM SHARED vWeekly as C
DIM SHARED vDay1 as C
DIM SHARED vDay2 as C
DIM SHARED vDay3 as C
DIM SHARED vDay4 as C
DIM SHARED vDay5 as C
DIM SHARED vDay6 as C
DIM SHARED vDay7 as C
DIM SHARED varC_result as C
ok_button_label = "&OK"
cancel_button_label = "&Cancel"
varC_result = ui_dlg_box("Enter New Dosage Info",
{endregion};
%dlg%,

[Steve Workings]

RE: Xdialog, trapping Enter Key

Doing some self-prescribing are we now Jim? Did you increase doseages based on your fun with this?

You'll also be interested in Cal Locklin's work with enter key on XDialog -- see further down the topic list about 2 days ago I think.

- Steve

[Peter.Wayne]

RE: Xdialog, trapping Enter Key

jim,
not sure what you want but this should work:


{endregion};
%dlg%,
but that gets more confusing, i think.