Visual Style Builder: Improve control structure navigation, save state of filtering, provide information about inherited theming
Control Structure Pane - For example, RadForm has a RadTitleBarElement, which contains no styles, because they are inherited from the RadTitleBar control. Here we can add a note, which says from which control the styles are inherited:
Design / Preview Pane - Click on an element from the Design view and select it into the control element tree.
Elements Pane - Add an option to expand all sub-nodes in the Control Structure tree. Save the setting for the filter chosen by the user.
Find repository usages: Add an option to expand all sub-nodes.
Repositories - Sort applied repositories on top or in another list. Currently, we can see all the applied only when we click "Show only applied repositories".
Repositories - Add an option to filter the repositories by type(font, fill, border, image, and so on). Currently, we can filter them only by name.
Dinko | Tech Support Engineer
Posted on:21 Sep 2023 09:59
I appreciate the provided feedback. The resizing behavior of the expander row comes from the GridViewElement used in the structure of the Elements section inside theapplication. This is leftover functionality is probably it could be removed. As for the property section, you have a point that maybe adding this to a global task could require more time to implement all functionalities. As you mentioned, creating a new time to allow resizing or taking up the available space in this section could be more easily planned. That is why I have created on your behalf a separate feedback item for this. This way you can vote for its implementation to increase its priority.
Thank you again for your valuable feedback.
Dinko | Tech Support Engineer
From a planning perspective, I worry that there are too many items here to do effective prioritization.
For example, I recently submitted a support ticket regarding the last item "PropertyWindow - Add an option to allow the property window to take all the available space, thus allowing you to see more property settings." . I had submitted this intending to highlight that it feels like a bug (imagine if you opened up a "File>" menu in office, and only 3 items appeared and you had to scroll to reach "Close"... it impacts basic usability. It's almost like if you tried to use Excel, and the "grid" portion of the active workbook didn't fill in the space to the bottom area of the window... ).
However, "Add an option to filter the repositories by type" is clearly a feature request, a desire to add more functionality than originally planned. I was directed here to vote on this item, but I worry that what may be a relatively low level of effort of setting a dock/fill + CanResize property may be lost against a monolithic task of a large and compound scope.
Attached shows that the non important content area can expand, while the primary data cannot. If the users should be able to vote in a way that lets features and fixes get prioritized, then each feature and fix should be separate.