The Scourge of Browsers
Cakewalk: Please make all browsers fully configurable. The latest generation of CW products is forcing unprecedented file structures. In my case, these structures conflict with the existing file structure on my PC in which I have multiple tools/instruments sharing sample directories, with programs located in folders grouped together, etc., etc.
The browser in X1 has many pages implemented that I cannot delete. While I can add and then delete the pages that I have added, the unwanted, unused default pages clutter the interface. I cannot imagine the logic behind making them persistent. It is as if the team that developed the browser was unaware of the paths specified in the global options. As a result, for example, I now have the default projects diretory, and my actual projects directory (which I added in the browser) and is specified in the global options.
I just loaded Z3TA+2. The readme file warns of the file structure that must be used for the browser to work. This again does not bode well for maintaining order and maintainability in my system. Admittedly, I have not tried the Z3TA+2 browser yet, but this constraint makes me think that it is not worth my time to try.
This makes me wonder whether the browsers for these products was a piece of canned application software and was not actually developed by CW. Please make the browser page content locations completely assignable. Users who prefer not to be bothered can use the defaults, and users like myself, can maintain a coherent structure for all of our tools while supporting maintainability such as simplified backup operations.