ProMaps

Version History

ProMaps.VersionHistory History

Hide minor edits - Show changes to markup

May 19, 2023, at 05:00 PM by 192.88.134.15 -
Changed lines 21-22 from:

https://www.seedcode.com/rootimages/stikipad/promaps/1055ScriptUpdate.png

to:

https://archive.seedcode.com/rootimages/stikipad/promaps/1055ScriptUpdate.png

Changed lines 27-28 from:

https://www.seedcode.com/rootimages/stikipad/promaps/1055MapData1.png

to:

https://archive.seedcode.com/rootimages/stikipad/promaps/1055MapData1.png

Changed line 31 from:

https://www.seedcode.com/rootimages/stikipad/promaps/1055MapData2.png

to:

https://archive.seedcode.com/rootimages/stikipad/promaps/1055MapData2.png

April 21, 2021, at 02:26 PM by KC Embrey - Added #upgrading
Added line 96:

May 26, 2020, at 10:10 PM by KC Embrey - Fixed HTML template link
Changed line 38 from:

If you have not made any custom modifications to either of these fields, you can download and extract the updated https://www.seedcode.com/rootimages/stikipad/promaps/ProMaps1.055HTMLTemplates.zip?, open each of the files with a text editor, such as Atom or VSCode, copy the contents, and paste them into the matching field in ProMaps

to:

If you have not made any custom modifications to either of these fields, you can download and extract the updated HTML template files here, open each of the files with a text editor, such as Atom or VSCode, copy the contents, and paste them into the matching field in ProMaps

June 23, 2019, at 06:18 PM by KC Embrey - Added instructions for version 1.055
Changed lines 3-9 from:

The build number for your copy of ProMaps can be found on the bottom edsge of the home screen or in the field Interface::BuildNumberCalc.

The latest build of ProMaps is Build 1.054 (September 28, 2018) This fixed an issue where the GeoCoding scripts were not functioning correctly after the Google Maps API billing requirements were enacted.

You can make this change in your copy by going to File -> Manage -> Database, editing the MapSettings::GoogleAPIKey field, and selecting the "Use global storage" option under the Storage tab. This will allow the GeoCoding scripts to use the API key when querying Google's servers.

After saving this change, you'll need to re-enter your Google API key in the ProMaps General Settings and click the "Apply Settings to Map" button.

to:

The build number for your copy of ProMaps can be found on the bottom edge of the home screen or in the field Interface::BuildNumberCalc.

The latest build of ProMaps is Build 1.055 (June 23, 2019) This build fixes an issue with the street-view and zoom button labels showing offset in the map views. It also adds support for FileMaker 18 version specific FMP URLs (will also work with future versions).

Implementing the changes

Here are the calculated variables used in these first two changes that can be copied and pasted into the calculations:

//Use version specific FMP URLs when possible
sc_appVersion = Left ( Floor ( GetAsNumber ( Get ( ApplicationVersion ) ) ) ; 2 ) ;
sc_fmpProtocol = Case ( sc_appVersion ≥ 18; "fmp" & sc_appVersion & "://" ; "fmp://" ) ;


Script changes

On line 34 of the "Export Map HTML" script, add the lines highlighted in the screenshot below to the "Set Field [MapSettings::HTMLExportGlob…" step:

https://www.seedcode.com/rootimages/stikipad/promaps/1055ScriptUpdate.png

gm_MapData calculation

Add the lines highlighted in the screenshot below to the gm_MapData calculation in your properties table:

https://www.seedcode.com/rootimages/stikipad/promaps/1055MapData1.png

Also in the gm_MapData calculation, update the popover links (3 of them by default) changing fmp:// to " & sc_fmpProtocol & " (shown in the screenshot here):

https://www.seedcode.com/rootimages/stikipad/promaps/1055MapData2.png

HTML Templates

Using a layout based on the MapSettings table (ProMaps Setup for example), go into layout mode and add the "MapDataTemplate" and "RouteDataTemplate" fields to the layout.

If you have not made any custom modifications to either of these fields, you can download and extract the updated https://www.seedcode.com/rootimages/stikipad/promaps/ProMaps1.055HTMLTemplates.zip?, open each of the files with a text editor, such as Atom or VSCode, copy the contents, and paste them into the matching field in ProMaps

If you have made changes to your MapDataTemplate or RouteDataTemplate fields, you'll need to make the following changes manually:

In MapDataTemplate, find the following line (around line 30)

#map-canvas img {

And change it to:

#map-canvas .gm-style-iw img {

Near lines 427, 476, and 635, you'll find lines that start with:

clickLink("fmp://[[fileHost]]/[[fileName]]?

Change fmp:// to [[fmpProtocol]] on each of those lines to use the version specific FMP URL protocol where applicable.

In RouteDataTemplate, you'll just need to find the line (around line 30)

#map-canvas img {

And change it to:

#map-canvas .gm-style-iw img {


Click the "Apply Settings To Map" button, or run the "Upon Opening" script to save the changes and reload ProMaps.


Build 1.054 (September 28, 2018) This fixed an issue where the GeoCoding scripts were not functioning correctly after the Google Maps API billing requirements were enacted.

September 28, 2018, at 10:36 PM by KC Embrey - Added build 1.054
Changed lines 5-13 from:

The latest build of ProMaps is Build 1.053 (April 28, 2017) This fixed an issue where the in-map buttons wouldn't fire scripts in FileMaker 16 (by enabling the fmurlscript extended privilege as described at the top of the page here).

to:

The latest build of ProMaps is Build 1.054 (September 28, 2018) This fixed an issue where the GeoCoding scripts were not functioning correctly after the Google Maps API billing requirements were enacted.

You can make this change in your copy by going to File -> Manage -> Database, editing the MapSettings::GoogleAPIKey field, and selecting the "Use global storage" option under the Storage tab. This will allow the GeoCoding scripts to use the API key when querying Google's servers.

After saving this change, you'll need to re-enter your Google API key in the ProMaps General Settings and click the "Apply Settings to Map" button.


Build 1.053 (April 28, 2017) This fixed an issue where the in-map buttons wouldn't fire scripts in FileMaker 16 (by enabling the fmurlscript extended privilege as described at the top of the page here).

September 19, 2017, at 05:50 PM by KC Embrey - contain -> constrain
Changed line 23 from:

Build 1.05 (August 15, 2016) This is a major new build which introduced a new interface, contain options, and routing to the map.

to:

Build 1.05 (August 15, 2016) This is a major new build which introduced a new interface, constrain options, and routing to the map.

May 09, 2017, at 01:16 PM by 192.88.134.15 -
Changed line 5 from:

The latest build of ProMaps is Build 1.053 (April 28, 2017) This fixed an issue where the in-map buttons wouldn't fire scripts in FileMaker Next (by enabling the fmurlscript extended privilege as described at the top of the page here).

to:

The latest build of ProMaps is Build 1.053 (April 28, 2017) This fixed an issue where the in-map buttons wouldn't fire scripts in FileMaker 16 (by enabling the fmurlscript extended privilege as described at the top of the page here).

April 28, 2017, at 05:12 PM by 192.88.134.15 -
Changed lines 5-19 from:

The latest build of ProMaps is 1.052 (September 13, 2016) This added some CSS to suppress a irrelevant browser warning on some Windows machines. If you'd like to make this change in your copy, instructions are at the end of the page in Troubleshooting.

to:

The latest build of ProMaps is Build 1.053 (April 28, 2017) This fixed an issue where the in-map buttons wouldn't fire scripts in FileMaker Next (by enabling the fmurlscript extended privilege as described at the top of the page here).

This also changed two scripts to restore compatibility with MacOS Sierra. You can make this change in your copy by modifying the last line in two scripts to add an additional forward-slash (/) to the url calculation:

In the "Export Map HTML" script, find the "Set Variable [$$sc_MapURL" statement. In the "Export Route HTML" script, find the "Set Variable [$$sc_MapRouteURL" statement and change this line in the value:
Substitute(sc_filepath ; "file:/" & sc_root & "/" ; "file:///")
to this:
Substitute(sc_filepath ; "file://" & sc_root & "/" ; "file:///")
Run the "Upon Opening ProMaps" script and your map should appear correctly.

Build 1.052 (September 13, 2016) This added some CSS to suppress a irrelevant browser warning on some Windows machines. If you'd like to make this change in your copy, instructions are at the end of the page in Troubleshooting.

Changed line 5 from:

The latest build of ProMaps is 1.052 (August 15, 2016) This added some CSS to suppress a irrelevant browser warning on some Windows machines. If you'd like to make this change in your copy, instructions are at the end of the page in Troubleshooting.

to:

The latest build of ProMaps is 1.052 (September 13, 2016) This added some CSS to suppress a irrelevant browser warning on some Windows machines. If you'd like to make this change in your copy, instructions are at the end of the page in Troubleshooting.

Changed line 7 from:

---

to:

Changed lines 5-9 from:

The latest build of ProMaps is 1.05 (August 15, 2016) This is a major new build which introduced a new interface, contain options, and routing to the map.

to:

The latest build of ProMaps is 1.052 (August 15, 2016) This added some CSS to suppress a irrelevant browser warning on some Windows machines. If you'd like to make this change in your copy, instructions are at the end of the page in Troubleshooting.

---

Build 1.05 (August 15, 2016) This is a major new build which introduced a new interface, contain options, and routing to the map.

August 22, 2016, at 11:10 PM by 192.88.134.15 -
Added lines 14-15:
• Don't delete your value lists. You'll be adding a couple more but can reuse some of the ones you have.
August 21, 2016, at 07:45 PM by 192.88.134.15 -
Changed line 7 from:

If you're upgrading from an older version, you'll find discounted upgrade pricing here. The changes from our old version are too numerous to make line-by-line in your file: every layout, and nearly every script, has changed. So the best way to upgrade is to integrate this new file from scratch: there are fewer layouts in this new version so it won't take as long as with the last one.

to:

If you're upgrading from an older version, you'll find discounted upgrade pricing here. The changes from our old version are too numerous to make line-by-line in your file: every layout, and nearly every script, has changed. So the best way to upgrade is to integrate this new file from scratch: there are fewer layouts in this new version so it won't take as long as with the last one.

August 16, 2016, at 03:50 PM by 192.88.134.15 -
Changed lines 5-7 from:

The latest build of ProMaps is 1.05 (August 15, 2016) This is a major new build which introduced a new interface, contain options, and routing to the map. If you're upgrading from an older version, these changes are too numerous to make line-by-line in your file: every layout, and nearly every script, has changed. So the best way to upgrade is to integrate this new file from scratch: there are fewer layouts in this new version so it won't take as long as with the last one.

to:

The latest build of ProMaps is 1.05 (August 15, 2016) This is a major new build which introduced a new interface, contain options, and routing to the map.

If you're upgrading from an older version, you'll find discounted upgrade pricing here. The changes from our old version are too numerous to make line-by-line in your file: every layout, and nearly every script, has changed. So the best way to upgrade is to integrate this new file from scratch: there are fewer layouts in this new version so it won't take as long as with the last one.

August 16, 2016, at 01:20 PM by 192.88.134.15 -
August 16, 2016, at 01:20 PM by 192.88.134.15 -
Changed lines 3-5 from:

The build number for your copy of ProMaps can be found on the bottom edge of the home screen or in the field Interface::BuildNumberCalc.

The latest build of ProMaps is 1.05 (August 15, 2016) This is a major new build which introduced a new interface, contain options, and routing to the map.

to:

The build number for your copy of ProMaps can be found on the bottom edsge of the home screen or in the field Interface::BuildNumberCalc.

The latest build of ProMaps is 1.05 (August 15, 2016) This is a major new build which introduced a new interface, contain options, and routing to the map. If you're upgrading from an older version, these changes are too numerous to make line-by-line in your file: every layout, and nearly every script, has changed. So the best way to upgrade is to integrate this new file from scratch: there are fewer layouts in this new version so it won't take as long as with the last one.

A couple tips:

• Don't delete your Home, Properties Map, Properties List, or Properties Details layouts: keep the layout, just delete their contents. You'll add new layout contents and script triggers as part of the integration instructions.
• Delete all your ProMaps scripts and fields: you'll reimport them from the new file.

August 16, 2016, at 01:14 PM by 192.88.134.15 -
Changed lines 3-15 from:

The build number for your copy of ProMaps can be found on the bottom edge of the About screen or in the field Interface::BuildNumberCalc.

The latest build of ProMaps is 0.71 where we moved the sync engine in ProMaps to GoZync 5. There were no changes to the "mapping" scripts or functionality. To move your deployment to GoZync 5, download the new GoZync, then follow the integration instructions here: GoZync 5 Integration.

The latest build of ProMaps is 0.70 where we moved the sync engine in ProMaps to the new GoZync 4. There were no changes to the "mapping" scripts or functionality. To move your deployment to GoZync4, download the new GoZync, then follow the migration instructions here: Migrating from GoZync 3 to GoZync 4.

Note that as of July 13, GZ4 hasn't shipped yet, so you may need to wait a week before we announce it and it shows up in dowloads. Don't worry, GoZync 4 is faster, and worth the wait =)

Build 0.67. This is our first public build and includes a number of changes from 0.65: We cleaned up script headers in all scripts. Cleaned up global and calc field names so they are consistant. Added a pending upload check when pulling new records. And we fixed a data encoding issue for data in popovers that was preventing the map from loading in some circumstances.

Build 0.65 (April 7, 2013). This is our "early access" build for folks who asked to get in on the beta.

Build 0.60 modded by John while Tanner was away in Twisp.

to:

The build number for your copy of ProMaps can be found on the bottom edge of the home screen or in the field Interface::BuildNumberCalc.

The latest build of ProMaps is 1.05 (August 15, 2016) This is a major new build which introduced a new interface, contain options, and routing to the map.

The history and documentation for earlier versions can be found here.

March 24, 2015, at 01:59 AM by 142.4.217.187 -
Added lines 4-5:

The latest build of ProMaps is 0.71 where we moved the sync engine in ProMaps to GoZync 5. There were no changes to the "mapping" scripts or functionality. To move your deployment to GoZync 5, download the new GoZync, then follow the integration instructions here: GoZync 5 Integration.

July 13, 2013, at 10:31 PM by 50.132.84.245 -
Changed lines 7-8 from:

Note that as of July 13, GZ4 hasn't shipped yet, so you may need to wait a few days. =)

to:

Note that as of July 13, GZ4 hasn't shipped yet, so you may need to wait a week before we announce it and it shows up in dowloads. Don't worry, GoZync 4 is faster, and worth the wait =)

July 13, 2013, at 10:30 PM by 50.132.84.245 -
Changed lines 5-6 from:

The latest build of ProMaps is 0.67. This is our first public build and includes a number of changes from 0.65: We cleaned up script headers in all scripts. Cleaned up gloabl and calc field names so they are consistant. Added a pending upload check when pulling new records. And we fixed a data encoding issue for data in popovers that was preventing the map from loading in some circumstances.

to:

The latest build of ProMaps is 0.70 where we moved the sync engine in ProMaps to the new GoZync 4. There were no changes to the "mapping" scripts or functionality. To move your deployment to GoZync4, download the new GoZync, then follow the migration instructions here: Migrating from GoZync 3 to GoZync 4.

Note that as of July 13, GZ4 hasn't shipped yet, so you may need to wait a few days. =)

Build 0.67. This is our first public build and includes a number of changes from 0.65: We cleaned up script headers in all scripts. Cleaned up global and calc field names so they are consistant. Added a pending upload check when pulling new records. And we fixed a data encoding issue for data in popovers that was preventing the map from loading in some circumstances.

Changed line 13 from:

Build 0.60, modded by John while Tanner was away in Twisp.

to:

Build 0.60 modded by John while Tanner was away in Twisp.

May 13, 2013, at 11:33 PM by 98.203.211.206 -
April 22, 2013, at 05:02 PM by 50.132.84.245 -
Changed lines 5-6 from:

The latest build of ProMaps is 0.68. This is our first public build and includes a number of changes from 0.65: We cleaned up script headers in all scripts. Cleaned up gloabl and calc field names so they are consistant. Added a pending upload check when pulling new records. And we fixed a data encoding issue for data in popovers that was preventing the map from loading in some circumstances.

to:

The latest build of ProMaps is 0.67. This is our first public build and includes a number of changes from 0.65: We cleaned up script headers in all scripts. Cleaned up gloabl and calc field names so they are consistant. Added a pending upload check when pulling new records. And we fixed a data encoding issue for data in popovers that was preventing the map from loading in some circumstances.

(855) SEEDCODE
[email protected]
Follow us: