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/27 17:50] – added Beta 2 of 9.5.2 James Sentman | current:beta [2024/02/05 17:51] (current) – 9.5.5b1 James Sentman | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | =====Beta | + | =====Beta |
- | **XTension 9.5.2 Beta 2 (2/ | + | |
- | A second | + | This is a beta release |
- | This beta fixes a problem with the most recent release that rendered the non-scripting dictionary commands to older interfaces like the Vera unavailable. These commands now work normally again. | ||
- | If a volume is missing or not mounted when a video plugin attempts | + | **This version makes no changes to the format of the Database so returning |
- | ----- | ||
+ | If you’re not interested in the history and why the support folder needs to be moved skip to the next section. | ||
- | **XTension | + | ===Changes to the location of XTension’s data files=== |
+ | 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 in the Users Documents folder and the Database and other support files were placed there. You can also continue to use XTension as it was in days of old and run it from any other folder on your drive. If you do this the database and some support folders are created along side the app inside this same folder but an XTension support folder is still created in the Documents folder. | ||
- | There is a beta version available | + | The location |
- | Download | + | |
- | This version contains important fixes to the new video system. This build fixes issues | + | It is my advice |
- | A minimum disk space of 100m is maintained with a default of 5gb. Depending on the number of video streams | + | ===Process |
+ | When first run XTension will look for an XTension Support folder in your Documents folder. If it exists in that location but not already in the Application Support folder it will move it and startup normally. Giving | ||
- | Only files inside | + | ===Switching to Running in the Applications Folder=== |
+ | If you are running XTension in the legacy way of being anywhere but the Applications folder you do not have to move anything manually yet. However at some point Apple may enforce that applications have to live in the Applications folder. If you wish to make the change now you can move the XTension application into the Applications folder. Then move all the support folders | ||
+ | |||
+ | ===Returning to a previous version=== | ||
+ | |||
+ | 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 to iCloud it will open a startup messages window advising you of this and suggesting that you turn that off. This info is also saved in the database so that if someone sends me a database to debug I can check easily if this is the source of some of the problems. | ||
+ | * If the database has already suffered some kinds of corruption from being shared to iCloud there are many things that it can now clean up. This includes deleted units or scripts | ||
+ | * The XTension Support folder is moved from the Documents Folder to the Application Support folder. Unless there is already a Database in an older version | ||
+ | * 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 for debugging purposes to find out just went wrong in the other script. | ||
+ | * Quite a few major OS versions now Apple changed Applescript to be somewhat, sometimes, unpredictably threaded. This allowed the application to continue to process commands and events while another script might have still been running. This led to confusion and things no longer happening in a linear and logically consistent order. I fixed that back in the day by pausing the command queue while a script was running so that even if the app got control back no more commands would be processed until the current script being run was complete. I recently added some new RTS cameras of higher resolution to my system which is pushing my older Mini a bit and I started getting more regular strange scripting errors that rarely | ||
+ | * 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 that could be logged when deleting more than a single page of Units from a list is now suppressed. It was never a useful error message so no fix was necessary, it’s just confusing debug logging. | ||
+ | * Errors that would sometimes be logged when closing the Interface list window while doing CPU and Memory use displaying in the “show more information” mode are no longer logged. Again these were just over zealous debugging messages and did not indicate a real problem. | ||
+ | * Fixed the incorrect display of version information. The version logged and in the About window will properly show 9.5.5 beta 1 in this case rather than 0.0.0.whatever as it did in some previous versions. | ||
+ | * 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 to the memory used and object count displays to make figuring out things easier. Most of you have never opened this window from the debug menu and won’t ever need to but it is helpful while I am testing and debugging and could be useful to help gather more info if needed from any of you. | ||
+ | * Added another debug menu option to log the current state of the globals “thisUnit”, | ||
+ | |||
+ | |||
+ | [[https:// | ||
- | There are no other changes to this build from the last release of 9.5.1, so it should not cause any new problems. It also makes no changes to the database layout or structure. If you do need to revert you should not have to revert the database to the backup that is made automatically when this build is first run, but it will be there if you need it. | ||
- | If you suspect an issue with the new disk space management or wish to see debug log output of it’s functioning and what files it chooses please go to the preferences and check the “show debug menu” checkbox. Then in the newly visible debug menu select the "Log Disk Space Management Info." When in debug mode the scan will be run every minute instead of every 5 to collect more debug data which will be written to the log in a lovely orange. You may also use the “Run DiskCheck Now” menu item to force it to run while you’re watching. Uncheck the “Log Disk Space Management Info” menu item to go back to normal functioning. Be aware that other options in the debug menu are undocumented and may cause more problems than it’s worth to play with them. Please do not use other debug menu items unless I ask you to in order to collect more info on other issues. | ||
- | -James 2/25/2023 | ||
current/beta.txt · Last modified: 2024/02/05 17:51 by James Sentman