ui_get_text vs xdialog

[Cheryl Lemire]

I have created a script 'serialnum' using the prompt for text: ui_get_text. It works great in most instances.

When I try to play my 'serialnum' script in the OnDepart event of a form field object, the script runs twice :(

If I create a new script using xdialog instead of the ui_get_text, it works properly and only runs one time when played from the same OnDepart event of a form field object.

Is this normal?????????????

this is the prompt for text:

'Prompt user for serial # at runtime

dim prmpt_title as c 
dim prmpt_prompt as c 
dim prmpt_default as c 
dim prmpt_format as c 

prmpt_title = "Process Receiving"
prmpt_prompt = "Enter your serial #"
prmpt_default = ""
prmpt_format = "&&&&&&&&&&&&&&&&&&&&&"    'restrict input to 21 character maximum

DIM GLOBAL vcgSerialNum AS C

vcgSerialNum = ui_get_text(prmpt_title,prmpt_prompt,prmpt_default,prmpt_format)

this is the xdialog:

'Create an XDialog dialog box to prompt for parameters.
DIM SHARED vcgSerialNum as C
DIM SHARED varC_result as C
heading_string = "Enter the serial number for the next piece"
ok_button_label = "&OK"
cancel_button_label = "&Cancel"
varC_result = ui_dlg_box("Process Receiving",<<%dlg%
{region}
{text=55,1:heading_string};
{endregion};
{region}
serial number:| [.40vcgSerialNum];
{endregion};
{line=1,0};
{region}
<*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
{endregion};
%dlg%)

[Cheryl Lemire]

correction

Actually, with further testing I find the same results with the xdialog. I think the issue has something to do with timing and perhaps the order I am trying to process things .... and/or the OnDepart event itself.

I have attached a sample so hopefully somebody can give me some ideas on how to accomplish my task.

To duplicate:

From the main menu, select the shipping/receiving button
From the shipping/receiving menu, select the enter line equipment button
enter your batch number - can use anything here - abc, 123
enter your customer po # - can use anything here
enter your serial # - suggest using the following series - abc, def, ghi, 123, 456 (checks for existing so use suggestions)

Form is loaded with auto popup list
Select any company
press the enter key to leave the company field
now at amserial field, no data needed, press enter
model auto pop up list, select any model and enter to date in field
except default date and press enter to activate ondepart event

dialog should prompt for serial number
use a serial number not yet used as suggested above

here you will get the model pop up list, and another serial number prompt .... the model pop up does not work right now and the serial number prompt will pop up several times depending on what you click on

I believe this is somehow a timing issue, but cannot seem to figure it out. To get out of here and look at the code: click on the return to main menu button on the toolbar ... select NO to save changes .... there is a hotspot on the main menu under the day of the date display.

The form is receiving, ondepart event of the date_in object

what I need to happen at this point: prompt for serial number
populate company, cust po, batchnum, and serial num based on variable values
activate the model field object popup so user can select model
once model is selected, go to date in field

then repeat the process to enter new serial number with same field data populated

To exit the application, go to the startup form, or the mnu_ship and click on the Exit application toolbar button

[Tom Cone Jr]

Cheryl,

If this is a double post I apologize. My browser is acting up this evening.

If your Date_in field is last in tab order remember that Alpha five will begin a new record automatically when you tab through it. Perhaps your script is confusing Alpha Five as it tries to begin a new record.

I'm unable to help you further. Your database is locked down. System menus are disabled. You've hidden the menubar, toolbar, and window bar. I can appreciate that these steps are needed before release, but these are the last things I do on a project not the first. I like being able to use the trace window, the system menu, and being able to toggle easily between view and design modes. I recommend you remove all the shackles during development. Work on the data entry and navigation sequences. Get the app running before you spend any time nailing down the specific user interface that you want to deliver. My 2 cents.

-- tom

[Cheryl Lemire]

I have attached a new sample without the db being locked down.

The date_in field object is the last in the tab order. How do I avoid the conflict?

Thanks

[Tom Cone Jr]

Cheryl, I don't think I can help you.

Your onDepart event script is probably triggering the OnDepart event itself, creating a loop that causes the repeating dialogs to display. For example, your onDepart event script shifts focus to objects on the form, and begins a new record, and then saves it. These sequences will generate other events as the form tries to repaint and resynch itself. You can trace events through the trace window, so maybe this will furnish some leads for you. Otherwise, I think you'll be better off moving the script to a button. I recommend OnDepart be used to validate the data just entered, or to shift focus to other objects.

-- tom

[martinwcole]

although Tom's explanation is more and better detailed, a work-a-round Selwyn gave us several years ago:

you will periodically run into double firings on many object events. when I run into one, I use the following.

dim global busy as L
if busy
     end
end if 
busy=.t. 'now the script won't keep firing
'script, etc. goes here
'when finished
busy=.f. 're-enables the script

[Cheryl Lemire]

Thanks Tom. You DID help me :)

Otherwise, I think you'll be better off moving the script to a button. I recommend OnDepart be used to validate the data just entered, or to shift focus to other objects.

I added a button to be next in tab order after the date_in form field object and moved my code to the OnPush event of the button. This will make the user have to press the enter key two times, but it works as I need it to.

Thanks for the assistance.