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/25 15:20] – 9.5.2b1 James Sentman | current:beta [2024/02/05 17:51] (current) – 9.5.5b1 James Sentman | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | =====Beta | + | =====Beta |
- | There is a beta version available | + | This is a beta release |
- | Download for all supported architectures: | + | |
- | This version contains important fixes to the new video system. This build fixes issues with the disk space management that could lead to the drives you’re storing video to filling up. The program now properly honors your settings in the video plugins setup pages where you set a minimum disk space to keep available on the disk. It will scan every 5 minutes and remove enough of the oldest files across all of the managed folders to bring the available space back up to your minimum setting. | ||
- | A minimum disk space of 100m is maintained with a default of 5gb. Depending on the number | + | **This version makes no changes to the format |
- | Only files inside the folders you select for the video plugins are scanned and deleted if needed. No other folders on the disk are touched. This means that other things not part of the Video recording system might cause the disk to fill up, or to cause more video files to be deleted to keep the space available. | ||
- | There are no other changes | + | If you’re not interested in the history and why the support folder needs to be moved skip to the next section. |
+ | |||
+ | ===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 | ||
+ | |||
+ | The location of the XTension Support folder has become an issue with Apple’s iCloud feature of syncing your Documents folder with iCloud. This service remains potentially a problem for many things but can and does cause corruption of the XTension database as files seem to be updated too often for it to remain in sync. It seems to restore files that were deleted as well as replacing new versions with older versions on occasion. | ||
+ | |||
+ | It is my advice to not use this iCloud feature at all as it causes the same problems with other files you may have stored in your documents folder. If you have this turned on you should turn it off immediately to avoid losing information. In the meantime moving the XTension Support folder to the Application Support folder will solve the problem for XTension **unless you are using XTension outside of the Applications folder but still somewhere under the Documents folder** in that case you must either switch to running | ||
+ | |||
+ | ===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 you a startup message window telling you exactly what it did. If there is already an XTension Support folder in your Application support folder and it does not contain a database then it will be renamed and the current XTension Support folder will be moved to the new location. If it does contain a database, even if it is an old one, then it cannot move it and will startup with that database along with a message that what appears to be your current database could not be moved and you will have to resolve the conflict manually. There should not be a live database in the Application Support folder however much earlier versions of XTension did use this location and so there may be old and outdated versions of information there that you may have to remove. | ||
+ | |||
+ | ===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 and database from the folder you used to have the App in to the Documents/ | ||
+ | |||
+ | ===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 | ||
+ | * If the database | ||
+ | * 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 of the folder that might exist in the Application Support folder. In which case no files are moved or deleted and a message is displayed asking | ||
+ | * Improved script error logging. Previously errors that were generated while running handlers in a different script were sometimes | ||
+ | * 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 | ||
+ | * 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 | ||
+ | * 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:// | ||
- | 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.1677338444.txt.gz · Last modified: 2023/02/25 15:20 by James Sentman