Differences

This shows you the differences between two versions of the page.

--- current:beta [2023/06/03 16:09] – formatting and bolding James Sentman
+++ current:beta [2023/06/05 13:49] – added beta 3 James Sentman
@@ Line 1: / Line 1: @@
-=====Beta Version (9.5.3 b1)=====
+=====Beta Version (9.5.3 b3)=====
-The currently available beta version of XTension is 9.5.3 beta 1 (build 1079) released on 6/3/2023
+The currently available beta version of XTension is 9.5.3 beta 3 (build 1081) released on 6/5/2023
-[[https://machomeautomation.com/files/xtension/xtension_9_5_3_b1.dmg|Download Xtension 9.5.3b1]]
+Beta 3 is continuing the cleanup of the new Hubitat unit types and is otherwise identical to beta 1 so I’m leaving those release notes below.
+[[https://machomeautomation.com/files/xtension/xtension_9_5_3_b3.dmg|Download Xtension 9.5.3b3]]
 Keep in mind this is a beta build and may contain bugs or annoyances and not all expected features or changes may yet be implemented. No database changes are made so if you to have to revert to the last release version simply replace the application with the previous version and all will be well.
@@ Line 66: / Line 68: @@
     * NEW: the [[dictionary:unitinformation:enumeratedvalue|Enumerated Value]] verb now accepts an optional parameter “for” and will return the correct enumeration for the value that you pass or an error if the enumeration is out of range. This is especially useful in the ON script of a unit as you can now check the enumeration for the future value to see what it is going to be when the script is done running. The direct parameter of unit name is now also made optional and if you dont specify it then it will use the value for thisUnit making it easier to script these in a units on or off script. For example: **write log enumerated value for (future value)** would write the enumerated value for the new value being passed to the On script.
     * NEW: The [[dictionary:unitinformation:changefuturevalue|change future value]] verb now also accepts enumerations just like the regular set value verbs so you can issue a change future value to “high” instead of just knowing what the numerical value is.
+  * **Xtension UI:**
+    * New: Each unit will get a new Unit Property called Created with the date the unit was created. You can add this to any List view by control clicking in the headers and selecting create custom column. Then you can sort lists by the date the Unit was created and not just the last activity date. For new Units this is set as they are created and then never changed. For existing Units the date is taken from the creation date of their folder within the database. This seems to work pretty well for most units most of the time, but there may be a date in the past where you restored a database or otherwise performed an action on it that would have reset those dates. This is still the best I can do but keep in mind that older Units may not show the date they were actually created, but the last time you zipped and moved the database or something like that.