current
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| current [2019/11/08 15:40] – 9.4.24 James Sentman | current [2019/12/07 15:54] – 9.4.27 James Sentman | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | =====XTension Version 9.4.24===== | + | =====XTension Version 9.4.27===== |
| - | Released: | + | Released: |
| - | \\ | + | |
| - | Download: [[https:// | + | |
| - | zipfile md5 = [[tech_notes: | + | |
| - | \\ | + | |
| - | Download for Catalina: (awaiting notarization, | + | |
| - | **NOTE!** not all plugins are included in the Catalina build. Please see the Catalina note below for more info.\\ | + | |
| \\ | \\ | ||
| + | Download: [[https:// | ||
| + | |||
| ====Important Info==== | ====Important Info==== | ||
| **Minimum System Version** for this release is OSX 10.10\\ | **Minimum System Version** for this release is OSX 10.10\\ | ||
| + | \\ | ||
| + | **Mac OSX Catalina** As of this moment I do not recommend that anyone update to OSX Catalina. Changes in Catalina have disabled several of the older plugins and the newer ones are not fully tested with it yet. As of this moment I do not recommend running Catalina on your house server. I don’t see any advantages and there are many potential issues not just with XTension. I can provide an Apple notarized DMG file of the subset of plugins that do work properly if this is something that you need. Otherwise do not update to Catalina yet for your house server.\\ | ||
| \\ | \\ | ||
| **Mac OSX Mojave** has changed the requirements for scripting of other applications. You MUST force any script to run that contacts a different application when you upgrade and click “OK” when it asks for permission or your scripts will silently fail when they run later. See the [[tech_notes: | **Mac OSX Mojave** has changed the requirements for scripting of other applications. You MUST force any script to run that contacts a different application when you upgrade and click “OK” when it asks for permission or your scripts will silently fail when they run later. See the [[tech_notes: | ||
| - | \\ | ||
| - | **Mac OSX Catalina** As of this moment I do not recommend that anyone update to OSX Catalina. I am supplying a Notarized dmg version of XTension that will run on Catalina. The regular zip file release and any previous release version will likely not run at all. Please see the [[tech_notes: | ||
| - | \\ | ||
| - | ====9.4.24 Change Log==== | ||
| - | * NEW: added “reset low battery flag” contextual menu item to the unit lists. If you have a unit that has a stuck low battery flag for whatever reason you can now reset it manually. If the low battery flag is actually coming from the interface it will reset itself as soon as the next command from the device is received though. | ||
| - | * NEW: added xtUnit class applescript parameters for the newer Group properties. You can now set the following parameters for Groups, they will have no effect if you try to use them for a non-group unit. They are read/write so you can query them or set them from another script. | ||
| - | * xtGroupBehavior | ||
| - | * xtTreatAsRadioButtons | ||
| - | * xtScriptsRunWhenAutochanged | ||
| - | * xtShowDimmableControls | ||
| - | * xtShowColorControls | ||
| - | * xtShowColorTempControls | ||
| - | * FIX: the xtUnit class property xtFlags now includes the correct battery level, if any, reported by the device. | ||
| - | * FIX: the xtUnit class property xtFlags no longer includes the no longer used “rfOK” flag. | ||
| - | * Totally rebuilt the internal handling of unit properties. They are now more abstracted so that they will be easier to use from other scripting languages once those are available. You can still store AppleScript specific parameters like lists and records but they may not be available to other scripting systems in the future. There should be no changes for how you’re using them at all. For the moment I am maintaining the data in the original format in the database so that if you need to revert to an earlier version of XTension you can do so without losing any data. After some number of releases without any bug reports on the new system I’ll remove those files. | ||
| - | * Change: Global Scripts now update their Last Activity date even if the script fails due to an error. Previously they would fail to update this if the script did not complete successfully. | ||
| - | * Change: Unit Properties are now sent through the Database Sharing plugins. The unit properties are synced in both directions. If you make a change on either side of the shared database connection the change will be sent to the other side. If you make a change on the receiver side while the connection is down or the interface is disabled then the receiver side will be overwritten by the data from the sender side when the interface reconnects. At this time the syncing of the unit properties is limited to Strings, Numbers and Dates. Applescript specific types like Lists and Records are not synced. This is possible to do so please let me know if you need this. | ||
| - | * The new RFX plugin for the older RFX and RFXe devices is no longer considered beta. I and several beta testers have been using it successfully now for months. Note that the newer devices are NOT yet supported by this plugin. Please make sure you’re connecting to one of the older protocol devices and that you select the Legacy protocol in the plugin setup dialog in XTension. The beta level support for that device will appear in the next XTension release. | ||
| - | * FIX: The previous rare but real occurance of the Vera, and potentially some other plugins become unresponsive is fixed. I was finally gifted a duplication of this problem by my own server after having been unable to duplicate it or figure out what was happening at all. It turns out to be a lower level system problem that hung up all networking for a short time. Not all plugins were affected, some seemed to recover just fine, others became suck in a hang down in the system. Since there was no error that could be trapped the only way to fix the problem was to implement a ping and restart system in XTension for the affected plugins. If a plugin of any type goes unresponsive for more than around 2 minutes XTension will quit it and start a new instance which does fix the problem. If the system does ever return a proper error from the networking level that will also result in the interface restarting to get itself running again. | ||
| + | ====9.4.27 Change Log==== | ||
| + | * NEW: Added a “Description” field to the Edit Scheduled Event window. This is just informational for you to describe why you created the event and what it is for. It is displayed as the tool tip in the Event List window but the way they implemented that it looks pretty horrid there, not like the tool tips in other display types. I’ll be updating that eventually but thats just cosmetic. It works just fine, just isn’t pretty. | ||
| + | * NEW: Added an option to “Ignore logging from Video Pitcher” on the Logging tab of the Preferences window. If you have one of those cameras that continually throws errors even though the stream is displaying this will declutter your log and make it easier to see real events. This does not suppress only errors but all logging from VP so if you’re having legitimate problems with something you may have to turn it off in order to see any actually useful messages from it. This is a temporary fix that will not be necessary once the new video plugin system is complete. | ||
| + | * FIX: Fixed an error in the AD2USB plugin that could have caused a Zone to be shown as in a fault state even when it wasn’t. The issue had to do with parsing the display data stream output in some edge conditions when using a high numbered zone id. | ||
| + | * FIX: In the new TP-Link/ | ||
| + | * Am filtering more garbage characters in the edit script window that can seemingly be inserted randomly by Apple’s VNC implementation. This should fix more of the problems that folks sometimes have when editing scripts over VNC where they fail to compile but show no location for the error as it is an invisible non-printable character that was inserted either randomly or more often in response to your hitting the delete key. | ||
| + | * FIX: the pigpio plugin no longer throws an error when setting the value of a PWM output pin that included a ramp rate property. | ||
| + | * FIX: the Recycle Interface verb no longer returns an AppleScript error even though it actually worked fine and did recycle the interface. | ||
| + | * This version returns to the new Apple file API version that will be necessary going forward to Catalina and beyond. Apple is sure keeping me busy working on this stuff that wasn’t broken last week. On earlier OS versions there should be no visible change to how anything works but please keep an eye on things when renaming Units or Global Scripts as this was where we had problems previously. Any errors will be written to the log if this happens so please let me know if you see anything while doing that. I have been running this fix on my own systems for several weeks now without being able to duplicate any of the previous errors so I don’t believe that anyone will have any new issues with it but let me know if it does. Note that this does not make it run any better on Catalina itself. Please do NOT update your servers to Catalina yet. I continue to work towards that capability. | ||
| + | | ||
| =====Previous Releases===== | =====Previous Releases===== | ||
current.txt · Last modified: 2024/02/05 17:53 by James Sentman