Search the Community

Ok so there was a previous 'UI Overhaul' post from a while back. But it seems to suggest, frankly, exactly the opposite of what I would like to see, so I can't upvote it. Therefore, new request time.. I've also posted this feedback in the '2024 - Icons' thread, but again not focused on what I want to specifically raise, which is about UI scaling and in particular icon sizes. We really need more customisability in icon sizes and scaling for different UIs. This was an issue before, but has got worse jumping from vwx 2023 to 2024. As you can see in screenshot below, on my laptop display (14", 2.8k, 16:10 aspect ratio), the icons and attributes take up too much screen real estate, and make it difficult to navigate to the various tools. This is always tricky to manage on laptops, however what I don't understand is why it has just been made worse. Ideally there should be a 'compact' mode for icons. Also, the 'attributes' part of the UI is really baggy compared to the rest of the tools and icons, and should be able to be made much more compact. Personally I'm also not a fan of the change in colours of the icons, which I find makes them harder to differentiate at a glance than they used to be, but this is more of a secondary concern. It would probably make everybody happy if an option was made available for black and white icons, or colour icons.

Is there a way to open a standard "open file " window to allow a use to select a file to be used as a resource list. I am in the process of a large symbol data update. i want to be able to open a "before update" file and have the user update the file with the newer symbol data base on a resource list created from a selected file. I don't see the need to create a resource list from all the file in the favorites folder, just one selected by the user. I could hard code this, but would prefer an file choice just in case this project goes beyond the one set of symbols (which it probably will). I just cant seem to find an open document procedure/ function anywhere. Thanks, Jeff