When deployin a fm17 form with a sub form on fm go - why does the whole form scroll like a carousel instead of the data refreshing ?
Update: I have had a bit of a play with this. If you create your own buttons with Single Step actions to Go to Record (next and previous), then the records will transition without sliding. With your own buttons on the layout, you can pretty much replicate all the native features of record navigation and then hide the toolbars for the user.
I believe you need to look at the 'go to layout' step in a script and look for "with animation". Or perhaps the script is calling a Slide panel? Can you post any script that might be called? It could be a triggered script. A layout mode screen shot can also help us give you better answers.
So just some details - initial post was on mobile..
I created a very simple app - loaded a master excel sheet of customers, then loaded a details sheet of customer transactions.
I linked the 2 tables via customer number
Created a single layout with the Customer details on it, then added a portal into the details table
Works really easily on Windows - select a customer- see transaction details. Select the next records & the form populates and the portal populates.
Added the same fmp12 file onto Filemaker go
Now when selecting next/previous record - instead of the form filling with new data - the whole "form" slides left or right - like a "Carousel"
I have no scripts - so was expecting a settig to control this maybe ?
The mobile app is designed to have the sliding animation when transitioning between records (next and previous). Are you saying you don't like that? Do you want it to look like the desktop and just flick to the next record? If so, I don't think you can change that on FileMaker Go.
(a two finger swipe left or right also navigates between records)
If the issue is that the layout is 'swimming' around when you drag one finger, it may be that your layout is too big for the device (iPad or iPhone) screen.
Have a look at one of the Sample files and see how big the layouts are that are designed for iPad and iPhone.
Generally, it is good practice to design specific layouts for specific devices (desktop, tablet, phone). Again, have a look at some of the Sample solutions to see the structure and scripting.
I did modify the size of the layout and reduced it, as well as selecting the iPad Landscape sizing. Below is the Windows view - an scrolling through records - the data change s- the fields stay in position.
Must admit I am not following newer UX design principles (like the samples) but more of an old school form with the record selector.
On iPad the view shows similar to above - but next & previous scroll the complete form not just the data in the fields/table
Retrieving data ...