Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 4325 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Has anyone seen this behavior in Go 12?

 

Simple portal of items on a layout....  Each has portal element has a category assigned (ex, animal, plant, mineral, etc).  There is a global for filtering the portal set as a pop-up of said categories.  Script trigger assigned to the global field to refresh window and commit when field is saved.  Desired effect is to keep Go from hopping to the next field when the global category selector is set.

 

Instead of the expected effect (click filter global, portal contents adjust, display stays put), Go refreshes correctly but then hops to the top of the layout to the first field and goes into data entry mode with the onscreen keyboard coming to life.

 

If I omit the commit step in the trigger script, the portal refreshes but the focus flows to the first field in the portal (as expected since the portal is below the global) and the keyboard pops up.

 

Things behave beautifully in the full fat client with the commit step in place.  Why is Go being a pain in the ass on this simple task?  Anyone seen this?

 

Thanks

This topic is 4325 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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.