Jump to content

NavSystem 1.0c

3 Screenshots

About This File

I wanted to see how far I could take the idea of using global repeating container fields to store layout objects, specifically for navigation buttons. This is what I came up with.

All image and text values that are displayed on the layout for navigation are stored in an "Objects" table. The benefit of this is that any layout that has the needed global repeating fields on it will display the same navigation buttons and text. Want to add more buttons? Just go to the Objects layout (click the grey globe button at the bottom left) and import an image or input new text values. The new option will automatically be added to all layouts.

What I really like about it is that everything is controlled by two simple scripts. "Main Navigation" and "Sub Navigation". And all they do is modify one of two global fields. Of course more script steps are needed to actually perform layout navigation or other jobs. I've included the structure that would be needed to facilitate that already in the scripts as you will see.

I've seen examples of this in a limited fashion, but like I said, I wanted to see how far I could take it. Thanks for any feedback or advice that you can offer.

What's New in Version 1.0c   See changelog


  • 1.0b
  • Fixed Error: SubNav options now appear for newly created MainNav buttons.
  • 1.0c
  • Fixed Error: Order of navigation script steps was corrected to allow for better handling of additional script steps.
  • NOTICE: In order for new MainNav buttons to work they must have a "dull" (non-selected) version as well as a regular one.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.