ignotum Posted December 9, 2009 Posted December 9, 2009 I have a single global text field on a layout. The script pauses at that layout for data entry, there is a button there that runs "Resume Script" and it works fine. I ALSO want the user to be able to hit the Return/Enter key to resume the script. That is not working. Depending on how I set-up the field I either get a carriage return in the field or nothing happens... I do this all the time... it works on other layouts... I must have something configured wrong on this layout of field... or is a property of the global characteristic...? Mark
ignotum Posted December 10, 2009 Author Posted December 10, 2009 So I've done some more testing. I changed the field from text to number.... same issue I created a fresh layout with the field in both txt and num formats.... same issue. Anyone have any ideas? Mark
LaurenKuhlman Posted December 10, 2009 Posted December 10, 2009 (edited) Hi Mark, I'll research it and get back to you. I have never heard of Globals causing this but we'll see. Edited December 10, 2009 by Guest
bcooney Posted December 10, 2009 Posted December 10, 2009 Do you have User Abort set to Off and all the Go to next field settings deselected? I can't get the Return key to not put in carriage returns, but Enter does "click" the Resume button. You could put a script trigger on the field to not allow crs.
ignotum Posted December 11, 2009 Author Posted December 11, 2009 But later in the same user process exactly that is working... hitting the large, right side of the keyboard RETURN/Enter key DOES trigger "Resume"...
ignotum Posted December 11, 2009 Author Posted December 11, 2009 Ok... I figured it out. The first pause/resume that was NOT working was in Browse mode, entering data in a global text field. The second pause/resume that WAS working was in Find mode, entering data in a number field. What turns out to be the fly in the ointment is the mode. The Return key does a Resume in find mode where it will not in Browse mode. There may be more to it that that... like the field's move to next field behavior, but I don't think the global property has anything to do with it. Any thoughts?
ignotum Posted December 11, 2009 Author Posted December 11, 2009 And while this is not a SOLUTION to the problem I changed this input to a real dialog and the dialog's OK button does, as expected, always resume the script regardless of the mode. (This was built a century ago in FMP 3 before dialogs with input fields were available...)
bobearl Posted December 11, 2009 Posted December 11, 2009 Hi ignotum, I was wrestling with a similar problem, but I'm one step behind you. What is your script step that allows the Enter to resume the script? The only way I've figured out to resume a script is with the pulldown menu in the button setup dialog (this may be different if you are resuming the script itself rather than a parent script). In any case, thanks for your thoughts. Cheers, Bob
Recommended Posts
This topic is 5462 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now