The improvements on LiveCode 10 keep coming and we are happy to bring you the latest in the lineup today with LiveCode 10 DP-3. This release includes a new charts preview in edit mode to make iterating your charts easier, support for the Map widget in the browser, a very welcome bug fix that stops the keyboard popping up for every touch on mobile and more….
Charts Widget – Live Preview
In the previous version when in Edit mode you were not able to see your chart changes until switching back to Run mode. That changes in DP3! The Chart widget now supports “live preview” – that is you can change its properties while in Edit mode and immediately see the result.
Note: The widget is still under intense development and as such there is a high chance that property names, features, and internal format may change in incompatible ways in subsequent DPs.
Map Widget – Web Support
The LiveCode Map widget will now work when deployed as a LiveCode Web app. In order to use the map widget on web, a Google Maps JavaScript API key is required, and this must be set in the configuration options in the Standalone Builder for the Map Widget inclusion.
A Platform Name Change
We have taken the decision to refer apps built for the web as Web Deployment rather than HTML5 deployment. Using “the platform” or “platform()” now returns “web” rather than “html5” when used in Web standalones.
Web Apps on Mobile – Keyboard Fix
Building web apps that work on all devices just got a whole lot better with this important bug fix on mobile. Previously when running your web app on a mobile device the keyboard popped up with any screen touch. In LiveCode 10 DP-3 we’ve squashed this bug and now your keyboard pops up only when expected!
Other Enhancements and Fixes
- Syntax has been added to LCB allowing encoding to, and decoding from, base64
- Syntax has been added to LCB allowing encoding to, and decoding from, a variety of text encodings
- The default content type used when doing POST or PUT requests on web has been corrected to “application/x-www-form-urlencoded”
- The “processor”/”architecture” of web standalones now reports as “wasm” rather than “js
- The revpdfprinter driver is now included with the server engine allowing open printing to pdf to work
- The default deployment platforms for a new stack are now appropriate for the current license
- Exiting fullscreen media playback will no longer cause a crash on iOS
- Folders added to the Copy Files list are now included recursively in web standalones
- Adding empty files to the Copy Files list will no longer cause standalone building to fail when targetting iOS
- The supported platforms of Mac Status Menu, Secure Key Storage, Time zone library and Drawing library extensions are now displayed correctly in the standalone builder
- Encoding text to utf16be using the textEncode function now works correctly on Windows
- The user guide PDF no longer has missing images
Known Issues
- The live preview of the Chart widget doesn’t appear when a chart is first created in Edit mode (Bug 23639)
- Changing the “chart type” property breaks the live preview of the Chart widget on macOS (Bug 23640)
- Changing properties of the Chart widget by script does not work correctly in standalones (Bug 23641)
The ones that didn’t quite make it…
In addition to the above we have also been working on lots of other improvements for LiveCode 10. Among some which didn’t quite make it into this release are:
- M1 Support for macOS
- Web platform support for the player control
- Engine-based JSON encoding and decoding
- Updated browser widget engine on macOS (WKWebKit) and Windows (Edge/WebKit)
- Snappier guidelines with magnetism support
Release Notes
For a full list of bugs fixed in this release please see the release notes, here.
Getting the release
To access LiveCode 10 dp-3, log in to your account and scroll down the list of available releases. You will find it below the full list of Stable releases. Not yet got a LiveCode license? Get one here.
2 comments
Join the conversationTom Glod - March 27, 2022
Quick question about the engine JSON library. Great idea, super needed. What will the library do when encoding and encountering keys that hold a binary value? ? baseencode?
Heather Laine - March 28, 2022
It will treat them as native encoded text – just like binary data is treated elsewhere in LC when you pass it to something expecting a string. JSON has no support for binary data so the engine won’t try and do anything clever – you need to base64Encode the values you want to do that with before passing to jsonEncode.