Once a portal is touched to scroll it, a footer with buttons
"back" and "next" comes up. Can this be suppressed in FileMaker Go 12?
I think the "back" and "next" refers to field entry. Is the cursor in a field in the portal?
No, all fields are locked in the portal. "Back" and "Next" appear before a row is selected in the portal. Even the scrolling causes the footer appears.
The behavior appears only on the iPad, not on the iPhon.
I found that the buttons are referring to the tab order of the fields. On a layout that I have where the portal row is highlighted when selecting through conditional formating and all text fields are locked the buttons appear, but when touching the Back or Next buttons goes to the next field in the tab order even though there is no field in which the text cursor is.
However if I touch on the layout ( not in any field ) to be sure no field is selected, then touch the scroll bar for the portal, I can scroll the portal and the Back and Next buttons do not appear.
Has anyone figured out how to hide this stupid records bar at the bottom of my iPad layout?
I hate it, it's totally ruining my layout. I have a single record database with a portal and I dont want the user to see anything else.
I can understand your anger.
I've helped methis way: after every action I save the record with CommitRecords/request () to hide the record bar.
JoE wrote: I can understand your anger. I've helped methis way: after every action I save the record with CommitRecords/request () to hide the record bar.
The bar appears as soon as the user scrolls. I don't see how I can assign an action to prevent this.
I was able to prevent the bottom bar from appearing by using FileMaker Advanced to put the solution in kiosk mode. The only minor downside is that Kiosk mode also hides the top bar. It does not actually make the top bar disappear as it does with the bottom bar, instead it simply replaces it with a black bar. If you are a perfectionist it will annoy you because it just looks sloppy to have this black bar throwing your interface off balance.
You would think that FileMaker could dedicate at least one person to user interface and make sure that none of this lazy/poor programming make it to the public release.
Retrieving data ...