Hello everyone. I'm beginning to test my solution on FM Go. I haven't used it much. On the desktop I have toolbars hidden and locked and am using a custom menu. I understand custom menus don't work on Go. I've hidden the menubar, toolbars, and editing toolbar on iPad. I've had to add an iPad menu to my layouts with some of the commands from the desktop menu.
The problem I'm having is that I don't know how to access the windows
You don't know how to access them on your desktop? Or you don't know how to allow them on iPad layouts?
All is well on the desktop. I have a custom menu bar. The problem is, when I hide the menubar and toolbars on the iPad, I can't figure out how to show the open windows. With the menubar showing, one can simply tap the window name at the top of the screen. This shows all open windows and allows the user to select the desired window. But without the menubar, how do I get there? Is it even possible? I'm assuming not, but I wanted to ask before I begin the task of resizing layouts to accommodate the menubar on the iPad. Thanks for the reply.
If you have the toolbar hidden then you will have to use script to manage switching between open windows, you would use the Select Window script step to switch bring a specific window to the front.
You also have the WindowNames {( fileName )} function that will give you a list of windows that are open, which if you wanted your user to select which window to open, you could tie in the a Virtual List technique and a card window to present a list of open windows for the user to select and then run the Select Window step to bring that one to the front.
Plus if you have got custom menus, as you know these do not work in FileMaker Go, you will need to add buttons or script triggers on your layouts to run these.
I hope this helps
-- Orlando
Thanks for the reply, Orlando. After playing around with it some more, I figured I'd need to roll my own navigation functionality. Thanks for the suggestions. I figure I'll add an "Open Windows" popover to my toolbar. Clicking it will show a portal with all open window names. Clicking a window name will execute a "Select Window" step. I could open a card as well, but I'd prefer to use a pop over because it would be more consistent with my UI in general.
I know how to do this by storing the window names in a related OpenWindows table. When opening the popover, I can use WindowNames ( ) to get a list of window names, compare that list to the list of related records, and modify the list of records accordingly by creating/deleting records in the related OpenWindows table.
I'm not familiar with the Virtual List technique. I did a little searching and found a bunch of threads and articles and examples, but I haven't had time to really study them. Knowing what I need to accomplish, if you can point me towards a good tutorial or thread that might help, I'd appreciate it.
Thanks!
No problem,
Here are a couple of links to articles for you to have a look at with regards to the virtual list, hope these are helpful.q
— Orlando
Thanks Orlando! Much appreciated! That second link was great. I've haven't even looked at the first yet, but the second one gave me all the info I need. What a great idea and perfect for my application.
...and ten minutes later, I have it working. That was really easy. I still need a relationship to the VirtualList table since I'm showing it in a popover, but that's no big deal. I'm starting to ask myself where else I might apply this technique. Thanks again!
If you have the toolbar hidden then you will have to use script to manage switching between open windows, you would use the Select Window script step to switch bring a specific window to the front.
You also have the WindowNames {( fileName )} function that will give you a list of windows that are open, which if you wanted your user to select which window to open, you could tie in the a Virtual List technique and a card window to present a list of open windows for the user to select and then run the Select Window step to bring that one to the front.
Plus if you have got custom menus, as you know these do not work in FileMaker Go, you will need to add buttons or script triggers on your layouts to run these.
I hope this helps
-- Orlando