Today we’ve released Beta 24, this one features the new Reveal Component, watch this weeks dev diary if you want to learn more about what it can do!
We’ve also fixed a whole bunch of bugs and instabilities — Especially relating to the editor and the resources area. As with each new beta, we can safely say, this is definitely the best version of Elements yet
Enjoy!
What’s New in Beta 24?
Added new Reveal component
Faster Document Loading (very noticeable on larger projects and slower machines)
Fixed issue with the scroll position resetting when changing anything in resources, page or project settings
Fixed Resource issue with thumbnails not loading and hanging/crashing the app
Fixed issue with Editor not updating when first opening a document!
Double clicking anywhere in a text component will now enter edit mode
Text Component now supports Borders
Button Component now supports different case styles
Fixed Property order for flex and grid
Fixed an issue with Text opacity colours
Add regex support to the expression parser for property hidden/visibility states in the Elements language
Fixed a crash when inserting new items while a filter is active in Page and Resources
Do not allow page deletion if there is only one page!
Fix editor initialization unnecessarily running multiple times
Under-the-hood memory management improvements for tree based views and more
Get the Update
Elements should prompt you while it’s running to let you know there’s an update. If it doesn’t, you can select the “Check for Updates…” menu option from the “Elements” app menu.
Please note: Sometimes it takes a while for the update to propagate. If you don’t see the update in-app, you can download the latest build of Elements from the confirmation email you received, as that link will ALWAYS give you the latest version.
Give Feedback
If you are using the beta, please post all feedback in the Elements Beta Feedback Forum. You can use the Elements > Send Feedback… menu item to automatically pre-fill the build number into a new topic.
Can I join the Beta?
We’re not taking on any more beta testers at this time; however, you should sign up here to be notified as more places become available.
@dan With this BETA 24 it seems to have broken something in the BUTTON component. When there is a drop zone present in the button the title is pushed to the left and the drop zone to the right.
If you set the button to have NONE for the drop zone the title stays pinned to the left. From what I can tell the title seems to be ignoring the justification text settings. Adding the drop zone to the left will cause both to be left aligned regardless of the justification setting.
UPDATE: this is still working perfectly in the browser, so there is something in the editor that is not working correctly. Buttons that were in a global do not seem to be affected, title alignment is correct.
Virtually all of the bugs I have reported have been squashed. It is looking good. Resources issues I was having, so far appear to have been fixed.
One issue that has not been fixed: Shift clicking in the text component still is broken. When you shift-click to select a measured amount of text, the editor will exit editing mode and just select the component itself. You can drag and select text as a work around.
Elements is looking good and is headed towards a solid release!!
Both examples are in this small project. Although in here the button is behaving differently than in my working project, but it is still not correct. There are also two resources, one remote and one local.
There are two buttons. The blue one I created from scratch and the red one I dragged in from my project. Both buttons display correctly in the browser but not in the editor. If you change the text alignment nothing happens to the text in the button. But it does the right thing in the browser.
I also added an example of a link to an anchor inside a typography component. It does not work in this component, but a link to an anchor does work in a TEXT component. Sorry I had tested this in this project with a TEXT component, not remembering the problem was in a TYPOGRAPHY component.
Thanks for the sample document, it was super helpful! The Button text issue is fixed in Beta 25 (available now-ish), and the other issues should be fixed in Beta 26 due later this week
