AnsweredAssumed Answered

FMGo15 unexpected changes?

Question asked by nickg on May 13, 2016
Latest reply on May 13, 2016 by nickg

I have a FM14 developed app that shows some odd differences when running on FMGo15 vs FMGo14.


On startup, the app opens a window ("GPS Tracker") with a webviewer that itself runs some JavaScript to monitor the GPS location every 15 seconds and sends the result via a FMPURL call into a global variable $$GPSLocation. Because the data are written to the global variable rather than to a data field, the script that responds to the FMPURL call is context independent. "GPS Tracker" displays the location data, converts lat-long to UTM and GBOS grid references, and chimes when a 1km boundary is crossed. It can also optionally log a track of all the points. The raw GPS data are displayed in the webviewer for debugging purposes. In FMGo13/14 this tracking continues to work when the GPS Tracker window is hidden.


The "GPS Tracker" is hidden on startup and the main window is then displayed, in which ecological field records are made. Because the GPS Tracker window updates the global variable $$GPSLocation in the background, the main window can display the current location using a merge variable <<$$GPSLocation>>. A button on the main window header brings the "GPS Tracker" window to the foreground if wanted (and the "GPS Tracker" window has a corresponding Hide button to switch back to the main window).


I hope that is clear so far ... now the unexpected changes:

1) the font in the GPS Tracker webviewer in FMGo15 is now tiny and has to be manually zoomed to be readable (just inconvenient)

2) critically, the GPS Tracker webviewer now stops running as soon as the GPS Tracker window is hidden, only waking again when the window is revealed. This is evident from the GPS raw data display in the webviewer, which does not update at all when the window is hidden (whereas is does continue to run in FMGo14).


So, it appears that the JavaScript thread in the webviewer no longer runs independently of the window, as it used to do in FMGo14. In FMGo14 the JavaScript only paused when the whole FM app was hidden on pressing the Home button or the iPad cover closed.


Apart from that, FMGo15 does appear more responsive and it does seem as though the terrible slow-down in SQL performance that came with 'upgrade' from FMGo13 has at least partially improved (I haven't run any tests to quantify by how much).


Is this change in background window behaviour intended? I haven't noticed any mention of it so far.


Has anyone else experienced this? Any suggestions for a workaround?