It has been documented that FM12 introduced some serious issues with the onlayoutkeystroke trigger on windows machines, especially when a barcode scanner is involved.  The issue is that the script trigger seems to interrupt the stream of characters coming in from the barcode scanner.  While this worked fine in FM11, this method is now useless in FM12 on Windows.

 

The recommended workaround is to add a global field to the layout, and use "onobjectexit" to return the cursor to the field after each scan.  While this works fine for simple cases, I am trying to migrate a FM11 file that uses the onlayoutkeystroke method to FM12.  The issue is that I have a rich layout with several action buttons and tab controls involved.  While I can script around the tab controls, I have been stuck at how to handle buttons in portal rows on this layout.  Clicking on a button inside a portal fires the onobjectexit script before the buttons script, so I can not use a global variable to disable the onoblectexit script.  

 

See the attached sample file for a skeleton breakdown of the problem (same problem on windows and mac).

 

Does anyone know of either:

A method to allow buttons inside of portals using the onobjectexit routine?

 

An alternate workaround that allows scanning input to be accepted while still having a rich layout with buttons in portals?

 

Any news on if the onlayoutkeystroke issue will be resolved for FM12 on windows soon?

 

It would be a serious setback for the functionality of the solution if users are required to bounce back and forth between a simple "scan accepting" layout and a more feature rich non scanning layout, but that is the only solution I can think of at the moment for FM12 on windows.

 

Any insights greatly appreciated.

 

-Raz

 

 

 

 

OnObjectExitProblem.fmp12.zip

Well, I popped in for just this problem.  Good to know it is not just me.

 

We scan the 2D Barcode from AAMVA ( Auto Titles, Registrations, ...) with a Honeywell 4600r.  I had setup OnKeyStroke to pick off the ASCII 31 Record Separators, and tack on a FileMaker CR/LF to the field, as it was scanning.  Was impressed the FileMaker 11 could do that.

 

I had even slowed down the scanner for 12, thinking it was just moving too fast.  At least I will not be wasting anymore time trying to get FileMaker 12 to actually work with this scan.  Will give the OnObjectExit a try first.  After that, I will just shelve it & check for fixes, on the new releases.