1 of 1 people found this helpful
Is the problem that you can't see what you are typing if the back-most field is the active one, or that 30% of the time you end up in the wrong field? or both?
And a few other questions arise, without knowing if they matter yet:
How is transparancy/fill set on the fields in 12? (Fills are different in 12 than in 11.)
Is either field in the tab order?
Is there any custom formatting on either field?
Thank you stephen,
Using the go to object script step, I end up always in the right field.
The first (the frontmost) object is the button fill = none
The second object is a calculated field fill = solid color
The third is the field for data entry fill = none, conditional formatting, script trigger on object enter and object modify (the target of the go to object script step).
Making some more testing, even if the active object is the right one, actually a global field, the cursor does not blink, and you type in the field but the field is invisible.
The only way to make the cursor blink is to press the tab key (but if I use the go to next filed scritp step i don't get the same result)
If I use the script debugger the behaviour is like in fmp 11
The field is in the tab order.
The annoying thing is that the same logic is duplicated in all the layouts of the solution, so changing it isn't a matter of minutes.
In filemaker go and in IWP everything is working as in fmp 11.
Can you replicate this behaviour in a new file?
It seems likely that the middle object with a calculated fill is blocking the appearance of your active field. Not expected behavior, and obviously unwanted behavior. The fact that FMP12 is not consistent with IWP/FP7 means it should be reported to FileMaker as a new issue.
Thank you Seve,
it's quite time consuming to replicate this behavior.
At the moment I've disabled the on object modify script trigger, and it works (it's upsetting but what else).
I've noticed that the problem may occur when the go to object script step try to bring the user in the target field but, even if is not active from the perception of the user, is already the active field.
(the active field is the target field, but the cursor is not blinking)
how I can report issues to Filemaker consistently?
At the moment I've got four issues that should be fixed.
1) Go To Object script step, to a target field that is already the active field but invisible to the user.
2) Insert From URL script step the changes a well formatted URL before submitting it to the web server (the last step out from Filemaker, so it's impossible to take control of the issue)
3) Go to Related Record script step, if you launch it from a layout that you view as a form and to reach a layout that is displayed as list the footer part of the layout doesn't display (it's white)
1) value list bug (view my post https://fmdev.filemaker.com/message/83822#83822)
I would email the discussion-thread on any individual topic to our Tech Liason with FileMaker, Dave Simerly. He is good about passing along stuff to the engineers at FMInc if they cannot be resolved here. Be sure to point out what has and has not been accomplished on a problem or bug so his work is simplified when he reviews the topic.
For anyone that will encounter the same problem, the solution is this.
Before using the Go to Object Script Step on a object that is already active but in the background (invisible), due to the fact that there is an overlapping object you need to use the script step:
Refresh Window 
then you use
Go To Object Script Step and the object in the background becomes visible.
In FMP 11 there was no need of the refresh window script step
(I've lost a huge amount of time changing a lot of scripts and layouts before finding this workaround)
I'm using FMP 12.0 V2