FM11A Script trigger firing out of sequence??

[mfl]

Have run into a "glitch" while testing FM11A Pro on our DB.

The DB is FM10A pro.

We have a main layout with multiple options for the user to select, basically a menu page.

Under FM10 everything works fine, but running FM11A there is one option that seems to go wonky.

I select this option and I should navigate to another layout where I have a choice of 3 more options, but sporadically it will drop the second layout behind the main menu layout and I can't get at it. I have to quit FM11A, but sometimes that doesn't even help.

I ran the select through the debugger and found that it runs a "OnRecordLoad" option which is not based on the second menu but runs when you select one of the options from the second layout.

This is the script that navigates to the second layout.

Enter Browse Mode 

Go to Layout [ “0100: Main: Translations” (Translations) ] 

Show/Hide Status Area 

[ Hide ] 

Set Window Title [ Current Window; New Title: "MONDETTA : Translations" ] 

If [ Get ( PrivilegeSetName ) = "[Full Access]" ] 

End If 

If [ Get ( PrivilegeSetName ) = "11 Orient Merchandising: Supervisor" ] 

Go to Layout [ “0110: List: Translations” (Translations) ] 

End If 

If [ Get ( PrivilegeSetName ) = "05 General Clerical: User" ] 

Go to Layout [ “0110: List: Translations” (Translations) ] 

End If 

Perform Script [ “0010 > Set Magnification based on Get (Screen Height)” ]

Anyone run into this??

Thanks

Michael L.

[Lee Smith]

I deleted your duplicate post.

[mfl]

Lee,

Don't believe there was a duplicate posting.

The deleted posting delt with FM11 not recognizing set layout dimensions.

In FM10 we set a layout to 5 x 5 px to reduce screen flicker and it functioned without issue.

In FM11 it doesn't recognize that setting and pops a layout that is about 1 x 1 inch in size.??

But no matter, the way things are going we may not upgrade to FM11, plus no one other than you wants to give any answers to my queries.

Thanks anyway

Michael L.

[Lee Smith]

I'm sorry, it sure sounded the same. My apologies.

Can you post a copy of the file you are talking about? We don't need all of the data, just the bare bones and a couple of dummy data records.

Also, you stated cross-platform, but are you developing on Mac or Win?

Don't give up on a ll quite yet, are you using the FMP Demo, or do you have Advance for 11?

Lee

[Vaughan]

The minimum window size issue is a documented change in FMP 11. It's caught a few people off-guard.

There are also changes in script triggers between FMP 10 and FMP 11, including new trigger types in FMP 11.

[Lee Smith]

Hey vaughan,

I'm know about the changes in script triggers, but I haven't experienced this widow phenomenon as of yet. Is this a Win or Mac or both problem?

Is there a white paper or something out there on this.

Lee

[Vaughan]

It affects both windows and mac (I think) and the minimum dimensions differ between platforms.

It was discussed on TechTalk some time ago.

Easy to test, open a new window then resize it to the minimum. Get the window dimensions.

[RodSierra]

It affects both windows and mac (I think)

Yes both, and it really hoses our menu bar feature, I certainly hope this gets fixed.

[mfl]

Lee, Vaughan,

At work I use Mac, at home its windows.

We have the full blown FM11A Pro at work.

Primarily its the Mac side I'm concerned about, don't do much dev work on the windows side yet.

The only way we got around this layout minimum was to designate a negative positioning so that it was of the screen.

Unfortunately there are way too many places where this is happening so changes are not going to happen.

I haven't even begun to test from windows side of things, we have users in China and its critical that it works flawlessly for them.

TechTalk where do I find that, is it a subforum?

Found this on the Filmaker site..

The Scripted Minimum Window size has been increased on the Mac

In FileMaker Pro 10 on the Mac when you executed a script step that set the size of the window, the resulting window size would always be at least 16x16.  It turns out that a window this small cannot accommodate our functioning view hierarchy, and when you would then do a “Resize to Fit” operation on the window, the values from the view system would not be correct, and the calculation would not be correct.  

To make the window resizing calculations come out correctly, we now insist on a window size that is just large enough to accommodate our view system.  The minimum scripted dimensions are now 110x144. This only affects the minimum window size when setting it through scripting.  The minimum size that is enforced when manually resizing the window is unchanged (and much larger than the scripting minimum).

Don't really want to be posting the DB in the forums, plus it might take a bit to delete records, dealing with 20 tables.

[Vaughan]

...it really hoses our menu bar feature, I certainly hope this gets fixed.

It's not broken, this is the new behaviour. There is some technical reason why that I can no longer remember, but it's here to stay... something to do with the minimum size required to display operating system window interface widgets.

[RodSierra]

Thanks Vaughn, looks like we will need to rethink this as its a popular feature. Letting the excess run off the bottom of the screen will probably be our choice for bottom justified, but for top we will now have to have another layout that is bottom justified so the excess will run off the top.

[Vaughan]

Anything that uses multiple windows won't be cross-platform. Since something like 75% of FMP licenses are Windows that cuts out a large slice of the market.

TechNet is the FMI FileMaker pay-to-play subscription forum.

[mfl]

So any idea why a script trigger would be firing early.

The process goes this way......

1. User logons on to the main layout. No triggers.

2. User selects specific option from menu( only this one option produces the issue in FM11 with the layout popping behind the main layout and making the app non functioning)still no triggers.

3. User selects option #3 from list of 3 options.( None of the other 2 options fire any triggers when layout loads)

4. User selects New Measurement Chart from button on screen , at this point the layout based trigger OnRecordLoad fires and everything goes to hell in FM11.

Script for OnRecordLoad...

7000 Measurement Chart Defaults: 7110 > Set Description for Drop Down List upon Exit 

Set Field [ MesChart_Defaults_List::MCMCDL_Drop_Down_Description ] 

Thanks

Michael

[comment]

A simple demo file showing (only) the problem would be useful.

[mfl]

So it seems that the issue has been resolved.

Seems the previous developer who still works here never explicitly went to the required layout. He just scripted a call to the DB and on the mac in FM10 everthing worked no problem, went to the correct layout.

In FM11 guess it got confused as to where it should be going and just threw up the first or last layout that was created.

I just hope this all works on the windows side.

Thanks to all for your help.