Difference between revisions of "CoreGUI Enterprise B123700"
Jump to navigation
Jump to search
Line 9: | Line 9: | ||
* A sizing issue in [[OpenWithCGUI]] has been resolved | * A sizing issue in [[OpenWithCGUI]] has been resolved | ||
* [[setupz2]] is no longer accessible, with the installer being removed as 1.2.4-Enterprise is now portable | * [[setupz2]] is no longer accessible, with the installer being removed as 1.2.4-Enterprise is now portable | ||
* [[setupz2]], [[setupz3]] and [[setupz4 | * [[setupz2]], [[setupz3]] and [[setupz4]] | ||
* An enhanced logging function for [[CoreSettings]] has been introduced with a new Dock menu for this mode. This can be used for debugging startup issues with [[CoreSettings]] | * An enhanced logging function for [[CoreSettings]] has been introduced with a new Dock menu for this mode. This can be used for debugging startup issues with [[CoreSettings]] | ||
* [[CoreSettings]] will now display in the titlebar the mode it has been started in | * [[CoreSettings]] will now display in the titlebar the mode it has been started in |
Latest revision as of 02:05, 16 August 2021
CoreGUI for Enterprise B123700 update release notes:
Warning: This build is a BETA variant. This should not be used in production.
Build Updates
- Unused resources have been stripped from CoreGUI, reducing the file size from 10MB to 6.8MB
- CoreSettings has the new quick menus introduced from the main CoreGUI 1.2.4 branch
- An issue in ICengine regarding processes starting incorrectly with arguments has been resolved
- A sizing issue in OpenWithCGUI has been resolved
- setupz2 is no longer accessible, with the installer being removed as 1.2.4-Enterprise is now portable
- setupz2, setupz3 and setupz4
- An enhanced logging function for CoreSettings has been introduced with a new Dock menu for this mode. This can be used for debugging startup issues with CoreSettings
- CoreSettings will now display in the titlebar the mode it has been started in
- An issue with CoreSettings incorrectly applying opacity causing a 'integer cannot be parsed' error has been resolved
- Security Settings in CoreSettings has been updated
- An error with CoreSettings starting setupz1 in multi-threaded mode has been resolved
- personalisation has been deprecated with links in CoreSettings removed
- The app version for f1 has been updated
- Unused argument handlers in f1 have been removed
- F1AutomatedDockApp will now automatically start when dock apps are started
Known Issues
- In core versions, checkboxes are not correctly displayed
- On some systems, tasklistz incorrectly shows an error for "Thread cannot be aborted or suspended"