current:beta
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
current:beta [2023/02/13 14:52] – external edit 127.0.0.1 | current:beta [2024/02/05 17:51] (current) – 9.5.5b1 James Sentman | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | =====Beta | + | =====Beta |
- | There is no beta version | + | This is a beta release of the next XTension |
+ | **This version makes no changes to the format of the Database so returning to a previous version can be done simply by placing the previous version of the application back into service. The default location of the XTension Support folder and possibly the Database within it are changed and it will be necessary manually move the folder back to the Documents folder if you need to roll back to a previous version. See below for more info.** | ||
- | =====Beta 7 Changelog: | + | If you’re |
- | * NEW: The Video Encoder plugin will now run an Interface Script handler when a new encoding is complete. Open the Edit Interface dialog for the plugin and click to edit the Interface Script. Use the “Insert” toolbar item to add a default handler to demonstrate how it works. The handler is called “newFileAvailable” and it will pass you 2 parameters, the name of the video stream the recording came from and the full path to the new file. like: on newFileAvailable( streamName, filePath) | + | |
- | * NEW: If you’re | + | |
- | * FIX: Units added to the list of shared items to the Home Kit are no longer in danger of getting an invalid Accessory ID. | + | |
- | * If you have Units that do not reload properly with this build as they were too broken before use the new trouble shooting functions now included in the Troubleshooting | + | |
- | =====Beta 6 Changelog: | + | ===Changes to the location of XTension’s data files=== |
- | * NEW: Direct support for ESPresence in the MQTT plugin. Simplifies using ESPresence devices with the MQTT plugin without having to do a lot of scripting. Turn it on in the Edit Interface dialog for the plugin | + | |
- | * NEW: If there are important errors during startup a new list window will open to contain them separate | + | There are 2 ways that XTension can be installed. If the application is placed in the Applications folder then a folder called “XTension Support” was created |
- | * NEW: Multiple Interface Collision Detection. Previously it was possible to create a situation where a unit was set to use 2 interfaces to receive, but one of them could have another unit with the same address which would keep the multiple interfaces from working properly. During | + | |
- | * NEW: MQTT Plugin now better handles server reconnects. | + | The location of the XTension Support folder has become an issue with Apple’s iCloud feature of syncing |
- | * NEW: MQTT Plugin now has a separate field for the outgoing topic. If updates | + | |
- | * NEW: MQTT Plugin now lets you set the QOS and Retain values | + | It is my advice to not use this iCloud feature at all as it causes |
- | * NEW: MQTT Plugin implements | + | |
- | * NEW: The Video plugins now insert all the event data that you create while recording with the record from “whatever” for 30 info “name | + | ===Process of moving the files=== |
- | * NEW: The video plugins now provide | + | When first run XTension will look for an XTension Support folder |
- | * FIX: Fixed a problem with the MJPEG camera streaming plugin | + | |
- | * FIX: Fixed an issue with the Amcrest API camera plugin | + | ===Switching to Running in the Applications Folder=== |
- | * FIX: Fixed a rare and unusual problem with syncing data between XTension and the plugins. This could have caused the loading of units from XTension to be short circuited | + | If you are running XTension in the legacy way of being anywhere but the Applications folder |
- | * FIX: The logging of available RAM that XTension does at startup was logging it with the wrong suffix showing that you only had kb available | + | |
- | * FIX: I’ve made it possible | + | ===Returning to a previous version=== |
- | * CHANGE: This shouldn’t affect anything, but keep an eye out in case it does. Plugins that have scripting handlers now register them with XTension. XTension will verify | + | |
+ | If you find this version to cause new problems, please do not just return to the previous version without letting me know exactly what the issue was that caused you to need to do so or it will be much less likely I can get it sorted out by the release. Without XTension running just move the XTension Support folder from the Application Support folder back to your Documents folder and then start the previous version. The Application Support folder is generally hidden from the User and may not be easily visible from the Finder. If so you can use the “Go” menu in the Finder to reveal the Library folder and inside that will be the Application Support folder. If XTension is still running you can use the Reveal Database In The Finder menu item from it’s Database menu, Then Quit XTension and do the move manually before replacing it with the previous version. | ||
+ | |||
+ | ====Changelog: | ||
+ | |||
+ | * At startup if XTension finds that your database is being shared | ||
+ | * If the database has already suffered some kinds of corruption from being shared | ||
+ | * The XTension Support folder is moved from the Documents Folder | ||
+ | * Improved script error logging. Previously errors that were generated while running handlers in a different script were sometimes not logged causing instead a generic error in the script doing the calling. They will now log more useful information | ||
+ | * Quite a few major OS versions now Apple changed Applescript | ||
+ | * Further new script debugging I’ve added the ability to log runtimes of individual scripts. You can turn this on in the Gear toolbar menu for any script be it an On/Off script or a Global Script. This may be useful if there is a script that sometimes seems to take a lot longer than it should be. Especially if that script is talking to an external app to wait for something. | ||
+ | * Errors | ||
+ | * Errors | ||
+ | * Fixed the incorrect display of version information. The version logged | ||
+ | * Made some additions and changes to the runtime debugger window to better sort items when there are more than 10k of any individual kind. I also added deltas | ||
+ | * Added another debug menu option to log the current state of the globals “thisUnit”, “thisScript” and “thisInterface” as well as the value of gCurrentScript internally which is used to direct handler calls of global handlers and other such things. These should all be empty with gCurrentScript being nil at any point that a script | ||
+ | |||
+ | |||
+ | [[https:// | ||
- | This is probably going to be the next release unless something else exciting comes up. | ||
- | =====Beta 4 Changelog: | ||
- | Change log: | ||
- | * NEW MQTT Client plugin. No wiki documentation yet. Read the information on the unit pages carefully. Select how you’re going to get the data out of the topic there are currently 3 types of parsing to get it out. There will be more for more complicated devices. Then enter the MQTT Topic into that field and if the Unit is 2 way select the way you’re going to send data back to the server. There are currently many choices but none that will yet easily handle XML or JSON values or more complex structures that would require scripted parsing and scripted re-creation of such a structure. If you have examples of such things please send me the topic data from them and as much other info as you can put together so I can make sure that the release version of the plugin can handle it. To see all the topics as published turn debug mode on for the plugin instance. Note that there is no attempt to automatically create Units for an MQTT server. That would result in a LOT of Units. Create only the Units you need with the specific topic paths that you wish. Use a problem like MQTT explorer to find what they are on your server. Also note that this is NOT a broker. This is a client and can connect to a broker elsewhere or running on the same machine. I recommend the Mosquitto server at the moment since that is what I have been testing against. | ||
- | * FIX data logged from a Unit using the contextual menu item of log debug data will now have the Unit set so that you can filter for that and see it in the log. Makes it easier to gather debugging information for me. | ||
- | * Fixed an error in the error logging in one place in the basic plugin includes. This could have caused a confusing error and would have stopped the logging of the actual error and information that I would need to fix that. This was initially plaguing folks with the Barix plugin as it was trying to convert older Units. I have found an interface on my system that also generates this error so I will be able to fix it now, but if we were working on this please send me the new error message to help me get this squashed and properly working | ||
- | =====Beta 1 Changelog: | ||
- | Changes in the previous beta. | ||
- | * NEW Plugin for No Hassle AV 4x4 HDMI switchers. [[supported_hardware: | ||
- | * NEW Plugin for No Hassle AV 8x8 HDMI switchers. [[supported_hardware: | ||
- | * FIX: Fixed a problem loading Unit Icon files that were not JPEGs. PNG’s and GIF’s load normally again. This was broken recently when I switched to a faster jpeg parsing library. | ||
- | * FIX: more bugs in the Phillips Hue plugin that would have caused an error, and then an error in the error handling when it tried to log the wrong data. | ||
- | * Database Format Change: For more than 5 years I’ve been keeping 2 copies of the Unit Properties data to make it easier should anyone have to revert to an earlier version after using the newer version. This build stops doing that and removes the old file potentially making the database quite a bit smaller and therefore faster to load and easier to manage. At this point if you need to revert to a version more than 5 years old you’ll have to use the backup file that is zipped up when each new version is loaded. Or just be OK with losing the Unit Properties from your database. | ||
- | * Enumerated Values for Units are now individually trimmed of leading or trailing spaces. So if you enter the values like “slow, medium, fast” the system will know you didn’t actually mean those spaces to be part of the enumerated values. | ||
- | * If a plugin has an empty description the name in the popup will no longer show an empty set of parenthesis after the name. |
current/beta.txt · Last modified: 2024/02/05 17:51 by James Sentman