If you manually choose a layout from the layouts menu it isn't included in the back history. This is a scripted back process, so it records only when you navigate via a button inside the UI. Once you link somewhere though, the forward is cleared out, in much the same way that a web browser would. If you've gone backwards, you can then also track back forwards. It doesn't remember your found set or sort order though, so be aware if you go back to a record that isn't in the found set you will alter the found set to include it. The back and forward will remember the layout, tabs and record that you were on previously.
The back and forward is to track your history in BaseElements and to be able to back track to a previous layout and record. The buttons are the Back, History, and Forward buttons respectively. The find interface isn't modified at all, you can do regular finds as well as constrain or extend, and because you have field access, you can right click for "Find Matching Records" as well as context dependent sorting.
Switch back your old window and use the back and forward buttons to go back to old layouts. You can then open a new window, and keep that found set for later. A sample use case might be to go to a list of related items, which automatically switches to list view.
#GITHUB BASEELEMENTS WINDOWS#
We've stuck with well known FileMaker conventions where possible and tried to use as many native user interface controls and methods.Ī couple of basic tips : First it's just FileMaker, so you can create new windows and switch between form and list at will. BaseElements is designed to be familiar to anyone who is a FileMaker Developer.
0 kommentar(er)
