current
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
current [2023/06/07 15:36] – James Sentman | current [2024/02/05 17:53] (current) – James Sentman | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | =====Download XTension 9.5.2===== | + | =====Download XTension 9.5.4===== |
- | > There is a Beta version available: | + | >2/ |
- | Released | + | Released |
\\ | \\ | ||
- | Download Universal Binary for all Supported OS versions; [[https:// | + | Download Universal Binary for all Supported OS versions; [[https:// |
+ | |||
+ | **This is an important update for NGROK users.** This updates the ngrok client to support the system changes they are making live. The older version will no longer be supported very soon. Anyone using ngrok tunnels should definitely perform this upgrade as soon as possible. | ||
**Minimum System Version** for this release is OSX 10.10 but not all plugins will function properly prior to 10.13. Please start the necessary work to upgrade to at least 10.13 or recommended 10.15 or newer. At some point in the near future it will no longer be possible for me to support anything prior to 10.13 and the video plugins will never work prior to Catalina. | **Minimum System Version** for this release is OSX 10.10 but not all plugins will function properly prior to 10.13. Please start the necessary work to upgrade to at least 10.13 or recommended 10.15 or newer. At some point in the near future it will no longer be possible for me to support anything prior to 10.13 and the video plugins will never work prior to Catalina. | ||
Line 11: | Line 13: | ||
**Rosetta Note:** While the entirety of the main app and all more recent plugins are Universal and run natively on Intel or Apple Silicon there are a few older plugins including the W800 and CM11 that are still Intel only. They run fine under Rosetta and you’ll never notice the difference. The only issue is that Rosetta is not included by default on the new Apple Silicon Macs. You’ll need to first run any Intel app, or do a get info on any app at all and select “open using Rosetta” then the OS will tell you that you need Rosetta and would you like to install it now. Once you complete that those plugins will run normally. | **Rosetta Note:** While the entirety of the main app and all more recent plugins are Universal and run natively on Intel or Apple Silicon there are a few older plugins including the W800 and CM11 that are still Intel only. They run fine under Rosetta and you’ll never notice the difference. The only issue is that Rosetta is not included by default on the new Apple Silicon Macs. You’ll need to first run any Intel app, or do a get info on any app at all and select “open using Rosetta” then the OS will tell you that you need Rosetta and would you like to install it now. Once you complete that those plugins will run normally. | ||
- | ====9.5.2 Change Log:==== | + | ====9.5.4 Change Log:==== |
- | + | ||
- | * NEW: [[supported_hardware: | + | |
- | * NEW: [[supported_hardware: | + | |
- | * NEW: New option in the Preferences dialog to Dont Stop A Restart With " | + | |
- | * NEW: List windows now display the number of Units in the List as well as the number of Units in an error condition or with low battery messages. This is shown in the title of the window after the List name. | + | |
- | * NEW: The [[supported_hardware: | + | |
- | * NEW: The [[supported_hardware: | + | |
- | * NEW: The [[supported_hardware: | + | |
- | * NEW TEMPORARY: I have made some changes to the standard off handling in the Hubitat that fixes some oddness with enumerated commands. I believe this works for all existing devices as well but just in case there is a new checkbox in the hubitat settings that will allow you to drop back to the old handling if it causes you any problems. Please let me know if you have to use this for any reason and the details of that otherwise I will be removing it in the next version unless I hear from people with the need to do this. | + | |
- | * NEW: The [[supported_hardware: | + | |
- | * NEW: Those same Hubitat status messages are now automatically added to a Unit property called “Status Message” and another Unit Property “Status Timestamp” will be the date/time when the current message was received. This way you can trap them in a script, or add a custom column to any List window to show them if you wish rather than just logging them. The above checkbox for logging the status messages does not have to be turned on to send this info to the Unit Properties. This is always done. | + | |
- | * NEW: The [[supported_hardware: | + | |
- | * NEW: Added support for Ramp Rates to the [[supported_hardware: | + | |
- | * NEW: Added several options to the [[supported_hardware: | + | |
- | * NEW: The CPU Usage figures for plugins shown in the Interface List window when “show more information” is selected now includes the CPU usage of any helper apps or sub processes that the plugin might be running. This makes them much more accurate and useful for very CPU intensive plugins such as the Video plugins or the rtlamr or other plugins that use helper apps. | + | |
- | * NEW: The Interface List window also shows a percent of memory use for the plugin instance and any child processes after the CPU Usage number. | + | |
- | * NEW: A new option in the Interface List window lets you chose if the CPU Usage calculation is done based on 100% a single CPU core, or 100% being every CPU available in the machine. So if you have 10 cores and you chose individual then 100% would be using a full core, but per machine that would only be 10% of the overall machine load. Whichever makes more sense to you when viewing it. The numbers are usually very low and so many not show up on the graph at all unless you increase their values by setting it to per CPU. Plugins that are using GPU resources or that are using helper apps may show as using more than 100% if per CPU is selected. This is OK. | + | |
- | * CHANGE: The helper app for the Video system that does the encoding is now a proper background app and so will not show up in the dock as it is running. | + | |
- | * CHANGE: The [[supported_hardware: | + | |
- | * CHANGE: The [[supported_hardware: | + | |
- | * CHANGE: The [[supported_hardware: | + | |
- | * The [[supported_hardware: | + | |
- | * The [[supported_hardware: | + | |
- | * FIX: Found a problem with the [[supported_hardware: | + | |
- | * FIX: If the [[supported_hardware: | + | |
- | * FIX: The [[supported_hardware: | + | |
- | * FIX: Added a random pause up to 3 seconds when starting up multiple [[video: | + | |
- | * FIX: An [[video: | + | |
- | * FIX: The [[supported_hardware: | + | |
- | * FIX: Older binary plugins such as the Vera plugin would throw errors when trying to issue some unit specific scripting commands. This was due to the changes in the previous version that allowed the scripts to throw applescript errors if you called a handler that did not exist. The older plugins were not registering their handlers in the same way and so fell afoul of this. They will now let you call any of the handlers without an error. | + | |
- | * FIX: Fixed some problems with the managed folder system that is used by the new video plugins for managing disk space on the recording volume. This will now properly keep the minimum disk space you have set available. If you suspect something is going wrong with this there is an option in the new Debug menu (see below) that will let you log it’s progress and calculations to the log which you can then send to me for debugging. | + | |
- | * FIX: The managed folder system now recovers from having a volume not present at startup, or if a volume is unmounted and then re-attached. It will let you know if the Volume is unavailable and then will begin scanning it again when it re-appears. | + | |
- | * DEBUG: Added a checkbox to the preferences for “show debug menu” this will reveal a debug menu where I have gathered many of the various hidden debugging options in the app for easier access when it is necessary to gather more info for me on a problem. Please do not experiment with these unless I’ve asked you to as they may generate huge amounts of log output or break other things if used incorrectly. | + | |
+ | * The [[supported_hardware: | ||
+ | * Fixed a problem with the [[supported_hardware: | ||
+ | * Fixed the error that was logged while trying to create a symlink to the internal python version if you did not have a / | ||
+ | * The python symlink is now created inside the XTension Support folder “pythonxt” and you can use that to run python scripts inside XTension or from elsewhere but using the XTension settings. It is especially useful if you are running python scripts from an async shell script in XTension as they will inherit all the path info to run properly where running the built in python may cause errors. | ||
+ | * NEW: Added an option to delay quitting. This will popup a window asking if you really meant to quit, stopping accidental shutdown of the entire program due to misplaced fingers. The window will count down for 30 seconds and then quit the app. This window does not come up if the system tells XTension to quit as if before a restart or something similar. Find the checkbox to turn it on in the Preferences. | ||
+ | * NEW: Added the option to send a value of 0 for a dimmable Unit to the On script if there is no Off script. Normally a value of 0 for any dimmable unit will be sent to the Off script rather than the On script. Unless there is no off script. This meant that previously you potentially had to duplicate some of your logic for handling values in the On and Off script. When this is turned on in the Preference, and a Unit has no Off script. The On script will be run instead with the future value set to 0. This is on by default, but if it causes you issues with some of your scripting you can turn it off in the preferences window. | ||
+ | * Fixed the incorrect link to the mailing list signup page in the purchase dialog. | ||
+ | * Removed some debug logging I failed to remove before the last release. This was in the conversion of potentially confused strings into floats and so did not affect every plugin, but might have logged confusing information occationally. | ||
+ | * There was a change in AppleScript support in OS versions from Ventura on that would actually enforce some, but not all, of the scripting dictionary flags that have never, in the entire history of the Mac, mattered. So us developers got sloppy and failed to add things like the “optional” flag to all the verbs reliably. The first I’ve found and fixed was with the Speak verb where it would tell you that the “in” parameter was required. It is no longer required. So far I have not found any other such issues and a visual search through the dictionary did not reveal any more such issues, but it’s entirely possible there are more parameters that are not properly marked as optional. If you find any such errors please let me know. | ||
+ | * The Interface list window can now be sorted by CPU Usage, Memory Usage and Process ID. This only works if you have the “show more information” option turned on in the gear menu on the window. This can be a great aide in finding the plugin process that is eating up all your CPU or memory and linking a python process shown in the Activity Monitor to the plugin it’s actually running. They all just say “python” in the monitor. But now it’s easier to find the PID number in the list if you sort by it. | ||
+ | * Updated the [[xtension_manual: | ||
+ | * I had previously hidden some of the lower level debugging aids in the contextual menus by having people hold the option key while right clicking. There is really no need for this extra step so I removed it. The Contextual menus for Units and Interfaces will have their “log debug data” and “Reveal in Finder” options at the bottom of all the contextual menus for them. This will make it easier to collect info for me if things start behaving oddly. | ||
+ | * I added the same debug logging info to the contextual menus of global scripts should it ever be necessary to get a look at that. | ||
+ | * To that debug output I added another line of info comparing the length of the Unit Address in both bytes and glyphs. This might be helpful to more easily discover if a plugin or a bug somewhere has inserted invisible characters into the Address field of a Unit causing things to get disconnected in the database and potentially making more and more units being created when there really should be only the one. | ||
+ | * There were some significant updates and improvements in the main program libraries that will make many things run faster and smoother. So far my testing of all of them work just fine. They aren’t a thing I can turn off though, they are just part of the latest compiler update. It will depend on what you’re doing, how busy your machine is and how fast it is in general whether you’ll see any difference at all. Usually the things they improved aren’t an issue until you’re doing something many times in a row. So I expect that the main improvements will be in window redrawing and things like that, but if you have a machine that is very busy it may improve that somewhat throughout. | ||
----- | ----- |
current.txt · Last modified: 2024/02/05 17:53 by James Sentman