one way (of many ways) would be to store a route list - a return-delimited list of layout names. Then you would use a global field or variable as an index. Finally - Go to Layout: by Name ... using GetValue ( $$yourRouteList; index ).
(The buttons would increment or decrement the index and then go to the layout by name.)
Hi David, thanks for your fast reply!
Thats exactly what i mean!
The idea is that i can easily ad or delete layouts/test and only have to ad or alter the route list.
Since i've only been working on FM for 3 months now, i still have to take a closer look to the global and $$ functions....
I wil try figure it out this weekend, but feel free to ad some more pointers
HI, i got kinda stuck in the end...Lack of experience and knowledge..
The posted links are really helpful, i do understand them but i can't figure out how to reproduce them.
For example the list of layouts, i got them in a table where each layout name is in the next column, so the route order is from left to right. But then how to get it index and listed so the script can fetch next?
Maybe i need to learn more of the basics, since i seem to lack some knowledge...
If anyone got some example files i could use for learning or copying purposes, please do share!!
this works, but would be clunky to use because you'd need to have access to the layout with the layout name field from everywhere in your solution. You'd probably be better off using a global text field to hold a ¶-delimited list (mentioned above).
layout nav.fmp12.zip 66.7 K