Child pages
  • New in 7.4

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

https://support.servoy.com/browse/SVY-5984

https://support.servoy.com/browse/SVY-5876

https://support.servoy.com/browse/SVY-5772

https://support.servoy.com/browse/SVY-5964

https://support.servoy.com/browse/SVY-5876

https://support.servoy.com/browse/SVY-5967

https://support.servoy.com/browse/SVY-5984

https://support.servoy.com/browse/SVY-5166

https://support.servoy.com/browse/SVY-5683

SVY-5406

https://support.servoy.com/browse/SVY-5250

https://support.servoy.com/browse/SVY-2834

 

Mobile Client

  • SVY-4448 Added support for related find/search
  • SVY-4989 Enhanced the debug mode of the Mobile Client to read the Solution design live from Servoy Developer
    Since Servoy 7.3 code changes made while debugging are synced between the debug client and Servoy Developer. However, if the debug session would end and then restarted, the debug client would not have the latest code. In Servoy 7.4 the debug client reads the latest code from developer when launched, so it will always have the latest code, instead of having to do a full export if there was a code change made since the last export
  • SVY-5336SVY-5164 Improved Mobile Export Wizard
    The Mobile Solution Export Wizard has been improved by remembering all settings of the previous export and allowing to press the Finish button on the first page of the Wizard if there was a previously successful export that can be repeated based on the stored settings. 
  • Switched to JQuery Mobile virtual click events to work around the standard 300ms delay for click events on mobile browsers
  • Improvements to ListView performance
  • SVY-5406 Added option to configure the order of inclusion for additional JS & CSS resources 
    See  the Mobile Solution Export Wizard
  • SVY-5528 Added option to not auto-sync on first log in
    If the first form of the Mobile solution is not bound to a datasource, then the Mobile Client will not automatically perform a sync if the Solution is started for the first time. It is then up to the developer to call the sync method before accessing data. This way, the developer has control over how and when to perform synchronization and error handling in case of issues during the sync.

...