Custom Menus
SeedCodeComplete3.CustomMenus History
Hide minor edits - Show changes to output
Changed lines 3-13 from:
We usually include custom menus to add some new functionality to a menu. For example we've modified the File menu so that you'll see an "Import vCard" option if you view that menu from the contact's layout.
Note that Custom Menus can only be modified in FileMaker Advanced, but the ''scripts'' called by these menus (which is where the real work is done) can be edited in Pro or Advanced.
!! In Navigation
We use a custom menu to hijack the behavior of the Form, List, and Table buttons, so these run our script "View As ( Form ; List ; Table )" instead. This script is very easy to modify if you add a new table or section to SeedCode Complete.
Probably the most interesting use of Custom Menus in SeedCode Complete is in the creation of new records.
(:include NewRecords:)
Note that Custom Menus can only be modified in FileMaker Advanced, but the ''scripts'' called by these menus (which is where the real work is done) can be edited in Pro or Advanced.
!! In Navigation
We use
Probably the most interesting use of Custom Menus in SeedCode Complete is in the creation of new records
(:include NewRecords:)
to:
We go pretty light on Custom Menus in SeedCode Complete as they are not supported in WebDirect and we wanted as much parity between the platforms as possible.
The main use of Custom Menus is to give folks the ability to exit out of [[Edit Mode]] if they get stuck in there. All edit mode panels should have Save and Cancel buttons available, but this may not be the case when making a change in development. You can use the Script Debugger in FileMaker Advanced to get around our modal edit (if you have the proper privileges), but this script should help if that's not available.
%center% %width=440% http://www.seedcode.com/rootimages/stikipad/complete13/RecordOpenMenu.png
The main use of Custom Menus is to give folks the ability to exit out of [[Edit Mode]] if they get stuck in there. All edit mode panels should have Save and Cancel buttons available, but this may not be the case when making a change in development. You can use the Script Debugger in FileMaker Advanced to get around our modal edit (if you have the proper privileges), but this script should help if that's not available.
%center% %width=440% http://www.seedcode.com/rootimages/stikipad/complete13/RecordOpenMenu.png
Added lines 7-10:
!! In Navigation
We use a custom menu to hijack the behavior of the Form, List, and Table buttons, so these run our script "View As ( Form ; List ; Table )" instead. This script is very easy to modify if you add a new table or section to SeedCode Complete.
We use a custom menu to hijack the behavior of the Form, List, and Table buttons, so these run our script "View As ( Form ; List ; Table )" instead. This script is very easy to modify if you add a new table or section to SeedCode Complete.
Changed lines 9-10 from:
(:include New Records:)
to:
(:include NewRecords:)
Added lines 1-10:
!! How are Custom Menus used in SeedCode Complete?
We usually include custom menus to add some new functionality to a menu. For example we've modified the File menu so that you'll see an "Import vCard" option if you view that menu from the contact's layout.
Note that Custom Menus can only be modified in FileMaker Advanced, but the ''scripts'' called by these menus (which is where the real work is done) can be edited in Pro or Advanced.
Probably the most interesting use of Custom Menus in SeedCode Complete is in the creation of new records...
(:include New Records:)
We usually include custom menus to add some new functionality to a menu. For example we've modified the File menu so that you'll see an "Import vCard" option if you view that menu from the contact's layout.
Note that Custom Menus can only be modified in FileMaker Advanced, but the ''scripts'' called by these menus (which is where the real work is done) can be edited in Pro or Advanced.
Probably the most interesting use of Custom Menus in SeedCode Complete is in the creation of new records...
(:include New Records:)
