tonywhitelive

We might be having the same or similar issue.... Should FileMaker 14 on top of Windows 10 work? Client emailed with an error message: Title: Plug-in Installation error Body: “Unable to launch plug-in child process JVM" They have just 2 plugins that they use 360Works_Scribe.fmx64 BaseElements.fmx64 The install is FileMaker 14 on top of Windows 10. (previously running Windows 8=worked…looks like the upgrade to Window 10 that happened 7 days ago was the breaking change)

What are your top 10 scripts? Definition: The top 10 scripts are the top 10 Scripts showing in the scripts menu. These top 10 scripts should “first do no harm” as they can be accidentally called from keyboard shortcuts. Your top 10 scripts can include scripts that do something useful (and safe), or do nothing, for example: Script #08 with 0 steps. You might add some blank scripts to fill up the top 10 spots. If someone later adds a potentially damaging script, it will likely show up below the top 10, will not have a keyboard shortcut, and will be harder to call accidentally. Better yet, you can make your top 10 scripts useful… Here are some of the ones that we like: Go to MainMenu (System Wide Home Screen/Dashboard) Go to Detail View (goes to Detail view for the table that you are on) Go to List View (goes to List view for the table that you are on) Varies Varies Varies Varies Varies Varies Help Request (keyboard shortcut is a mnemonic for “call the operator") What are your favorite scripts to include in the top 10?

You could use a Button Bar with 6 Segments that calc their button segment labels using… GetValue ( SampleData::Text_Field ; Index/LineNumber ) …and “Hide (Segment) object when” IsEmpty ( GetValue ( SampleData::Text_Field ; Index/LineNumber ) ) Then add a parameter (1-6) to each segment…that you read into your script using Get ( ScriptParameter ). Use the GetValue function to map back to the course code

Hold that thought. We are retesting and having a hard time reproducing the "Hide object when' fail. More soon.

Hi Tom, We did some testing using the “Hide object when” feature while watching the Top Call Stats that resulted. The test in question was hiding a portal using a Slide Control, a Popover, and the “Hide object when” feature. A Slide Control or Popover did NOT produce a query to the related table. The “Hide object when” feature did. I plan on speaking with my FMI engineering friends at DevCon to reconcile what has been said with what our testing shows. Important topic.

Yours is a good and important question. One of the best ways to feed the need for speed is to prevented Containers and un-stored calcs from loading until you need to see them. Our testing seems to confirm that Containers and un-stored calcs that are on a Slide Panel that is never activated will NOT load. Putting Containers and un-stored calcs behind a Popover will keep them from loading until popped. The “Hide object when" feature does NOT seem to be as effective in preventing loading. Let us say that you have an record where you show 1 of 12 images. You might use a Slide Control with 13 Panels where the first panel is empty and you use a script to show 1 of the other 12 panels (and associated layout objects) on demand. Conversely, I would expect that stacking 12 images would load them all, even if they were behind a “hide object when" calc. Sometimes we use 1 Layout with a Slide Control with panels of info Sometimes we use separate Layouts. Pros and cons to each approach.

Make a script named “Save Window Sizes and Positions” and tell the user to run that script before closing The “Save Window Sizes and Positions” script Uses the WindowNames design function to get the names of open windows Loops through the list or window names looking for windows that you want to restore (using the Select Window script step) Use Get functions and and set field to save window settings to a table Use a script named “Restore Window Sizes and Positions” to restore the windows Use onFirstWindowOpen to trigger a script that runs on open (or run the script from a button) Read the data stored about the saved windows Loop through the window data and use the New Window script step to open windows (from the correct context) with the correct name and position.

You will need to have a way to store the window locations that persists across FileMaker restarts. An Account table is good for this…either by itself or with a more relational structure: Account-<Account_Window>-Window When a user quits the system, use the OnLastWindowClose Script Trigger and store each window position as table data using Get (Functions) http://www.twdesigns.com/filemaker-15-functions-list/ When the user logs back in, use onFirstWindowOpen to trigger a script that uses Get (AccountName) to located the saved window settings for that AccountName. Then use the Windowing scripts steps: New Window, Move/Resize Window, etc. to restore the windows.

View File FileMaker 16 Card Windows FileMaker 16 Card Windows A Card Window is a new type of window (FM16) that is modal (only to its parent window), allowing users to open a “context independent” sub-window (showing a layout in the same file or an external file) without leaving the parent window http://www.twdesigns.com/filemaker-16-card-windows/ Submitter tonywhitelive Submitted 02/17/2018 Category Infographics

View File iBeacons and FileMaker Go 15 iBeacons and FileMaker Go 15 Lists some (but not all) Possible Use Cases for iBeacons and FileMaker Go 15 Provides technical information about the (new in FileMaker 15) RangeBeacons function Showcases the breadth and versitilility of the FileMaker platform (check out what the users have on their iDevices). Exhibits some useful documentation of the FileMaker platform that we have produced over the years. http://www.twdesigns.com/ibeacons-and-filemaker-go-15/ Submitter tonywhitelive Submitted 02/17/2018 Category Infographics

View File FileMaker 14 Code Objects as ERD infographic FileMaker 14 Code Objects as ERD infographic Provides a concise overview of "FileMaker code objects" that developers are well advised to be aware of. Shows some of the relationships between FileMaker code objects, and can result in insights that lead to better code. Shows some FileMaker version history, information that can be useful to developers and project planners. Contains some useful tips http://www.twdesigns.com/filemaker-code-objects-erd/ Submitter tonywhitelive Submitted 02/17/2018 Category Infographics

View File FMP URL protocol The fmp7://, fmp7script://, and fmp:// URL protocols offer FileMaker developers awesome possibilities. They can be used to control FileMaker solutions from outside or from inside. Examples include: from a web page, another application, or a FileMaker Web Viewer. http://www.twdesigns.com/fmp_url_protocol/ Submitter tonywhitelive Submitted 02/17/2018 Category Infographics