I have a field with a drop-down value list. As soon as an item is selected from the list, the cursor moves to the next field. I need the cursor to remain in the field.
For example, a value might be "Proceeding for the Appointment of a Guardian for ". I need the user to be able to select the value from the drop-down and then complete the sentence by typing a name.
Is there a way to accomplish this?
Thanks,
Kevin
Drop-down Value List Cursor Behavior
Started by steigrafx, Feb 05 2012 12:03 PM
6 replies to this topic
#1 OFFLINE enthusiast
Posted 05 February 2012 - 12:03 PM
#2 ONLINE I have an idea!
#3 OFFLINE enthusiast
Posted 05 February 2012 - 01:07 PM
Thank you very much, Ocean West.
I've copied your script and changed the field name and I've added [INSERT NAME]. into the entries in my value list, and I've set the script trigger but it doesn't work for me. For some reason, the [INSERT NAME] does not get selected and the cursor moves to the next field. I must be doing something wrong. I'll compare your other settings to see if I've overlooked something -- I'm sure I did.
Thanks again. I could never have come up with a solution like that. Amazing.
Kevin
I've copied your script and changed the field name and I've added [INSERT NAME]. into the entries in my value list, and I've set the script trigger but it doesn't work for me. For some reason, the [INSERT NAME] does not get selected and the cursor moves to the next field. I must be doing something wrong. I'll compare your other settings to see if I've overlooked something -- I'm sure I did.
Thanks again. I could never have come up with a solution like that. Amazing.
Kevin
#4 ONLINE I have an idea!
Posted 05 February 2012 - 01:17 PM
make sure you add the script to the trigger on the valueList field : i used onObjectExit
Stephen Dolenski
FM Forums.com Founder, Administrator
FM Forums.com Founder, Administrator
#5 OFFLINE enthusiast
Posted 05 February 2012 - 01:35 PM
Thanks. Yes, I did add the script to the trigger. I'm certain I've overlooked something. I'm going to double-check the script again.
Kevin
Kevin
#6 OFFLINE enthusiast
Posted 05 February 2012 - 01:49 PM
Okay...stupid me. I copied and pasted your script steps and then edited the field name. But, I wasn't paying attention. When I pasted the steps, the calcs came across as, for example:
"/*PatternCount ( Electronic Recording::Caption: ; \"[\" ) or PatternCount ( Electronic Recording::Caption: ; \"]\" )*/"
instead of
PatternCount ( Electronic Recording::Caption: ; "[" ) or PatternCount ( Electronic Recording::Caption: ; "]" )
Everything works perfectly now.
Thanks again,
Kevin
"/*PatternCount ( Electronic Recording::Caption: ; \"[\" ) or PatternCount ( Electronic Recording::Caption: ; \"]\" )*/"
instead of
PatternCount ( Electronic Recording::Caption: ; "[" ) or PatternCount ( Electronic Recording::Caption: ; "]" )
Everything works perfectly now.
Thanks again,
Kevin
#7 OFFLINE consultant
Posted 05 February 2012 - 02:59 PM
Now that you have a technical answer, here's an ideological one: use one field per fact.
Attached Files
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users
































