1 can we add ability to hide in view and zoom to the top?
Interesting request.
The current 'show/hide zoom' panel is currently written with the idea of operating globally on the entire model or on global elements such as all surfaces, all edges or all openings.
Your request is to add operations on a currently selected individual element such as a single roof surface.
In essence, this changes the underlying paradigm of the panel from global/individual thinking to visible/invisible thinking.
Let's say we agree that this would be a good idea. Then there are questions that need looking into:
What is the list of buttons we really want to be in the show/hides/zoom panel?
Should the space/storey/zone/cad id buttons also appear here?
If the latter should be in a separate panel then should an individual surface visibility toggle button appear in both panels?
And here's another thought:
In R12 all the fixing of issues is carried out in the right side context menu. The fixes are initiated by the user one by one.
In R14, there is the beginning of a move to automating the fixing process. The issues panel in the left menu is gaining more features. Eventually the fixing things scripts should replace almost all the need for a human to use the right-side context menu to fix things. Ultimately the fixing and viewing may end up being to completely different apps.
My gut feeling:
We wait until R15 to tackle this issue
Currently the code is in 'gv-sel-select-attributes' and it should be in 'gv-gbx-gbxml-loader'
We build two or three prototypes to help us understand which paradigms speed up work flow
We offer the user a choice of context menu they can use - depending on their needs
@mdengusiak
See item #1
Interesting request.
The current 'show/hide zoom' panel is currently written with the idea of operating globally on the entire model or on global elements such as all surfaces, all edges or all openings.
Your request is to add operations on a currently selected individual element such as a single roof surface.
In essence, this changes the underlying paradigm of the panel from global/individual thinking to visible/invisible thinking.
Let's say we agree that this would be a good idea. Then there are questions that need looking into:
Should the space/storey/zone/cad id buttons also appear here?
And here's another thought:
In R12 all the fixing of issues is carried out in the right side context menu. The fixes are initiated by the user one by one.
In R14, there is the beginning of a move to automating the fixing process. The issues panel in the left menu is gaining more features. Eventually the fixing things scripts should replace almost all the need for a human to use the right-side context menu to fix things. Ultimately the fixing and viewing may end up being to completely different apps.
My gut feeling: