Portal Navigation Consistency 2
Using portals, for the purpose of record navigation, have their downsides. The most obvious of these, is the fact that portals reset when moving from one record to the next.
This can be disconcerting to the user who is familiar with user interfaces which do not "reset" your sidebar and seemingly adjust your selection.
In 2011 I showcased a solution to this problem called Portal Navigation Consistency.
With the release of FileMaker 12 and higher, the functionality previously covered had broken. Not only that, there were newer solutions made possible which allow for a less complex implementation.
Within this video, you'll not only find how to maintain the selection of your navigation portal, but methods for capturing details about the way a user is using the portals. You'll also be treated to a simple solution which will adjust your navigational portal no matter how the user navigates to the target record!
Comments
Thanks for the updated version
Thanks, I really appreciate the updated version for FileMaker 12 and 13.
I have found that you can
I have found that you can just set a field immediately after the GTRR script step and it will freeze the portal and not reset it after record load. Thoughts?
Will need to look into this
I'll have to try it out.
-- Matt Petrowsky - ISO FileMaker Magazine Editor
Filemaker 14 and scaling portals
Hi Matt,
love this technique. Now on filemaker 14 and on an expanding portal I cannot get this to work.
Looks as if the conditional formatting of the portal is not refreshing the $$max.portal.row.
If I resize the window it does. However upon scrolling it does not.
Any thoughts on this?
Thank you,
ole
A "get_scrollbar_position()" function is needed....(?)
THX Mat for your work!!
We like to use the portal row navigation in our projects. But one last thing we need to finalize the implementation:
the whole calculation does not work after scrolling.
If you scroll down and select one of the last visible records (of the first visible 8 recordsets for example), the selected item makes a big jump. That's because the scrollbar y_ position is not recognised in the calculation.
Any ideas to solve this problem?
Best regards
Simon
Problem solved :-)
Spend some time and figured out how I could jump from one RS to another in consideration of the scrollbar position.
Now everything works fine with this script!
It works dynamically (even if statusbar is visible (or not) OR fullscreen mode is set OR other objects are in top of the portal).
If someone is interested - drop a line here...
@Mat P.: I can also send you the code snippet so you can provide it here
Simon