Hi Jørgen, All
I do not have a standard proposal of how to implement double clicking.
My main point is for McNeel to be cautious about granting such a wish in a ad-hoc manner.
Like I stated double-click functionality is a very basic powerfull UI feature, it really deserves to be able to do more than just edit a parent block (among a few other things). This is part of what I mean when talking about “getting it right”:
The way this is currently implemented for block-edits is just a prototype setup IMO. It feels not thought through that only parent blocks can be edited and then the user has to resort to _BlockEdit anyway. It’s half of a solution causing more clutter than a single unambiguous way to edit blocks.
It makes sense for me too to edit blocks with double click, as does it make sense to activate a detail-view, or edit text objects or dimension text or…(am I forgetting any).
It would also make sense to me to turn controlpoints on or solid-points or enable/disable clippingplanes in this view, or…
@Pascal I’m pinging you at this point to wishify my setup for double click below:
If I would have to decide on double-click functionality for V6, I would set it up in a way that is transparent en not hard-coded. I imagine that there is mechanism to catch double clicks, a table customizable by the user will decide what action to take, based on the objects that were double-clicked.
In short: sort of like the setup of the delayed context menu but more elaborate: http://docs.mcneel.com/rhino/5/help/en-us/options/context_menu.htm
McNeel can decide on a vanilla setup but the user can customize that.
For instance I can setup double-click to apply curvepiping to curves when double clicked.
Imagine what possibilities it offers when the users can control what double click does via his/her own macro’s and scripts.
DC will show/hide mapping widgets.
DC will export the object, and delete it.
DC will report the objects layer
DC will report a curves length.
If these Double-Click tables could easily be interchanged it would be simple to have various setups for different tasks. Or make a setup for specific projects with task specific functionality.
One thing to mention that will need to be sorted out: double-click and selection ambiguity.
The selection menu pop-up, currently prevents double-click to be efficient in dense models. It would be needed that a double click is caught/flagged and passed through the selection-menu pop-up.
So if I double click and the popup asks if I meant to click the text or the block, if I decide either of the 2 they will be opened for editing regardless of the selection menu.