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

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

Recommended Posts

Posted (edited)

Hi Forum.  I am having a little trouble with some navigation with my master-detail layout.  It works perfectly fine on the PC, but no always on the iPad. 

I navigate from record to record with basic buttons tied to the appropriate script step (First, Previous, Next, Last).  Every time I click a button, the record changes fine, and fires an OnRecordLoad Script trigger (attached).  The purpose of this trigger is to scroll the portal to keep the current record (highlighted in the portal) centered in the portal.  On the iPad, it will only scroll the portal every other time I hit the button.  On the PC it always works.

Does anyone see something obvious I'm missing?  Any thoughts/ideas/help would be greatly appreciated.

Thanks

Steve

edit:  I'm playing with this on my Windows 8 laptop because I'm home, but always use my window 7 machine at work 

PPpic.png

Edited by Steve Martino
additional info
Posted

Hey thanks for responding, sorry if I wasn't clear. FM Pro Adv12 & FM Go 12

I changed things around a bit, only slightly helped.  What I was trying to accomplish, on a simple master-detail layout, was when I clicked on a portal row, it shows the record on the detail side (works), but then scrolls the portal on the master side 3 rows so the matching master record is centered.  It works fine on the PC, but only works on the iPad if I take the Commit Records script step off.  When I was testing this while my iPad was connected on the FM network (peer to peer), I noticed that after the script executes, the portal row stays highlighted for about 3 seconds, the loses its focus (which is fine).  When I copy the file directly to iPad and try it, the third portal row below the record stays highlighted.  If I try to add a commit records step, the portal scrolling doesn't work.

I also tried adding go to field and go to object.  Go to field pops up the on screen keyboard, and go to object just doesn't work.

Posted

So first thing first, when you select a record in the portal, you wanna grab its ID (record ID doesn't really work in 12, I think), and set a global field in the parent table with it. 

 

And I don't get the three go to portal row commands. I'd stay away from that.

You mgiht want to check this out: http://www.modularfilemaker.org/module/hyperlist/

Posted

Is this a file you created from scratch, or is this one that you are modifying made by someone else, i.e. a template provided by FileMaker or 3rd party developer?

Posted

@ Lee, it's one I made from scratch.  @AR  I will take a look at hyperlist, but this is more of a master/detail setup--simplified version more along the lines of this:
https://www.geistinteractive.com/2013/04/18/master-detail-mfm-module/

The 3 portal row commands move the active record up to the center of the portal.

I think I got it working (workable).  Just get some unfortunate flashing, even with freeze window. 

Tomorrow I'll put in sample names, etc. and post file

Thanks

Steve

Posted

Got it. I assumed you were using a portal from an Interface TO. My bad.

Did you follow the steps in the example file?

At any rate, you shouldn't use the GoToPortalRow scripts step consecutively a finite number of times because it will always just go down 4 times. Not sure what that would achieve. I doubt you can keep a selected record in the center of the portal unless you manually scroll to make it seem it's there. And again, I can't see the reason for it.

Why is your object named "ID"? And why are you committing the records right after going to them? 

This topic is 3427 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.