Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 8063 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I want a series of buttons across the top of every layout in every db for User navigation. Example: Home, Clients, Staff. Then, within Clients, the 'menus bar options would be 'Billing, Reports, etc. I am considering the differences between Pop-Up Lists, Pop-Up Menus and Drop-Down Menus. I believe that, by using globals, I can place anything in pop-ups (?) i.e. my own 'lookups' to active scripts (New Record, Open related DB) etc.)?

Current considerations: 1) If I use Pop-ups, the field would always 'display' the current selection and I would prefer it display the "main button title' after selection. Example: A user selects reports but when finished with reports, the Pop-Up field would still display 'Reports' - I want it to display "Client Menu' so they know to select it again to do other things. 2) Pop-Up behavior differences between MAC & Windoz might be irritating (confusing) to my Users, as they 'switch desks and cross-platform PC's regularly.' 3) Drop-downs appear to be my answer but I'm concerned about how much real estate they require. For instance, if I use global containers (if that's what drop-downs use), does the drop-down area below the button bar need to be empty? I 've only found one example of a drop-down and that is Cobalt Sky's NavBar, but NavBar does not allow a peek! I anticipate 4-5 'selections' within each drop-down.

So, if I can figure out how to create Drop Downs (smile), can I place these global containers(?) 'under' fields so they display (jump to the front) to allow selection but, after selecting, drop to the back for displaying and using the data fields occupying the same area? I hope that all made sense! smirk.gif

Posted

The style of menu you are talking about is based on use of the portal visibility technique, where a portal with transparent file and line attributes disappears from view (taking its contents with it) when the relationship it is based on is not valid.

There are quite a few examples floating around on various sites, but one such, which is directly on point for what you are discussing is available for download from the LauoutMode web site. The URL for it is:

http://www.layoutmode.com/techniques/expmenu.html

However, as you say, the technique does not save a lot of space, because there are severe limits to what can share space with the portal (in short, anything which has its upper right-hand corner placed within the portal bounds will appear and disappear with the portal - objects may encroach into the portal area from the left, but that is all).

Also, as you'll see if you download the demo from Layoutmode, the technique can cause a fair bit of 'flashing' when moving around between records. In some situations this is more troublesome than others...

Posted

I see what you mean. frown.gif It looks like I'll have to reconsider my options! Which is more important ... using up space or dealing with inconsistencies in Pop-ups? Thanks for the info. However, I am appreciative of the download file. It looks like I missed that one. And, it could be used in other limited capacities. Much appreciated, Ray! wink.gif

Posted

It is tricky to implement cross-platform, and it doesn't look as pretty, but you might also like to consider the technique for using standard pop-up fields to operate a navigation system.

An example of this is in the 'LayoutMenu' demo on my web site. You may have already seen it, but if not, it is at:

http://www.nightwing.com.au/FileMaker/demos/LayoutMenu.zip

At least with this method, you certainly can save a lot of space!

Posted

This the method (and the download file) I had originally decided on. I hesitated when I saw the posts regarding inconsistencies in cross-platforms. Is there a way to force the pop-up to re-display the original (or MAIN) selection, instead of the one selected? Get my drift?

smirk.gif

Posted

Yes. The field that the pop-up is operating on is generally a global field, and a script is triggered to activate the selection.

That same script can update the field to a default value (or any other value you choose - anything from the current time to recent racing results smile.gif ) before it concludes its run.

This topic is 8063 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

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