NVil Forum
General Category => Feature Requests => Topic started by: mightypea on October 02, 2013, 11:30:26 am
-
When running connect on a selection, it'd be great if it would leave the produced edges selected. Particularly when connecting faces, it's hard to then loop select the resulting edges.
As in this image:
(https://dl.dropboxusercontent.com/u/17715/BL_connect.png)
-
The polygon and vertex mode operations are done. I leave the edge mode operation as is because you may want to do further cut in some cases.
-
Hi IStonia,
I agree with mightypea that the change was needed, but have to disagree with the change made, as the function result is still inconsistent.
I leave the edge mode operation as is because you may want to do further cut in some cases.
In which cases? Those cases, if any, could also apply to cutting polygons, so why not have the polygons left selected? Sorry, but you need consistency with these functions, so (IMHO) a case of either leaving pre-selection selected, or having the created geometry selected, not different results from the same function.
It is a similar issue with some other tools/functions. Simple example:- "Loop Insert" There are 3 main options:
1: Auto ring selected edges. (function leaves created edges selected)
2: Selection only (function leaves nothing selected)
2: Manually selected (Function leaves created edges selected).
Another simple example, is "Create closed spline" / "Create open spline" (from edges). You select edges, create spline, and you are left with pre-selected edges selected, why is that? Do you think the user may want to create a second spline from the same pre-selection? Would it not be more logical to have the created object(spline) selected after it is created?
From my own point of view, I think that anything created should be what is selected after it is created, at least that way, you have consistency. IMHO of course.
Sorry for what may appear a bit of a rant, but inconsistency can be confusing, but even more (to me at least), annoying, and not good workflow.
-
there has to be a way to turn this off, most annoying fucking thing ever when you need to connect lots of verts and it keeps switching to edge mode on every successful connect.
-
there has to be a way to turn this off, most annoying fucking thing ever when you need to connect lots of verts and it keeps switching to edge mode on every successful connect.
The option is added.
-
Thanks mate!
-
there has to be a way to turn this off, most annoying fucking thing ever when you need to connect lots of verts and it keeps switching to edge mode on every successful connect.
The option is added.
So will you be making the context_cut tool consistent, so that by default the created (Cut) geometry is selected? As it is now, you have added an option to maintain pre-sub_object selection, but it does that anyway if sub_object selection is edges.
-
@steve I mostly connect by selecting the 2 verts and taping the cut key, instead of using the interactive cut.
-
@steve I mostly connect by selecting the 2 verts and taping the cut key, instead of using the interactive cut.
If you are pre-selecting vertex, then pressing "C", you are using the "Context_cut". (unless you have changed the default cut event actions)
-
same tool I just explaining I'm not using it the same way as you thought since I prefer to pre select
-
same tool I just explaining I'm not using it the same way as you thought since I prefer to pre select
You are using it exactly as I thought you where. I have made no mention of the interactive cut tool. I have been posting concerning the "Context_cut" tool and what selection is made after its use (either the pre-selection sub_objects, or the new created edges).
-
havet tried since the update but I would just assume it would be the old behaviour with this once this option is tunred off where it just does the connect and keeps my 2 verts selected. or turn the option on if you don't like that behaviour to have it select the new geo.
-
havet tried since the update but I would just assume it would be the old behaviour with this once this option is tunred off where it just does the connect and keeps my 2 verts selected. or turn the option on if you don't like that behaviour to have it select the new geo.
You appear to be only concerned with the results of "Context_cut" on preselected vertex. I have been putting forward a need for consistency (for what is selected after using Context_cut) for all preselected sub_object selections.
-
there has to be a way to turn this off, most annoying fucking thing ever when you need to connect lots of verts and it keeps switching to edge mode on every successful connect.
The option is added.
So will you be making the context_cut tool consistent, so that by default the created (Cut) geometry is selected? As it is now, you have added an option to maintain pre-sub_object selection, but it does that anyway if sub_object selection is edges.
I can add an option to make the selection to new edges for cut tool commands. And also an option to the tool of spline creation from edges.
-
I can add an option to make the selection to new edges for cut tool commands. And also an option to the tool of spline creation from edges.
You are not being serious are you? You really want to add even more options? No, there are far too many already.
If you cannot see the need for some consistency in the programme, then I am wasting my time.
-
I can add an option to make the selection to new edges for cut tool commands. And also an option to the tool of spline creation from edges.
You are not being serious are you? You really want to add even more options? No, there are far too many already.
If you cannot see the need for some consistency in the programme, then I am wasting my time.
I have noticed that could be too many options. But there are some questions
* How to define the consistency for all tools. for example, chamfer tool, should the selection be new polygons or edges? Should all the new edges be selected?
* Consistency may conflict with individual people's preferred workflow.
-
I have noticed that could be too many options. But there are some questions
* How to define the consistency for all tools. for example, chamfer tool, should the selection be new polygons or edges? Should all the new edges be selected?
Well, the chamfer tool is another inconsistency is it not.
Do you believe the current results of what is selected after using the function is correct? As it is, it can be nothing(chop off), or it leaves the original selected edges selected, does anyone add a second chamfer on top of the first? or, will any other tool be used on that original edge selection?
* Consistency may conflict with individual people's preferred workflow.
I do not see how inconsistency can help any workflow. I have been using Nvil \ Voidworld now for approx 18 months, and still have not been able to get a good workflow. In fact, in that time period, all those I have got to try Nvil/voidworld have not lasted long enough to get a workflow as they find it too confusing.
If you are concerned about individual peoples preferred workflows, then why did you change the default (what was selected after use) of the Context_cut tool? That as now made you add another option(to change it back) to the ever expanding list, and now you want to add yet another option to change the result yet again. How confusing can you make the programme?
-
The chamfer tool selection was suggested by a user. What is your expected selection?
-
I was trying out the feature suggested in this thread. I think mightypea idea is cool, but my workflow is like Passerby, I often select just two vertices or a few of it and use connect. So making edge selected as the default behaviour is annoying for me too, because most of the time, I just want to connect the vertices and not doing anything further with the edge. With the default behaviour I have an extra step to go into vertex mode again.
I do prefer the resulting edge being selected when I do connect in polygon mode and edge mode.
I suggest making another context cut tool that does what mightypea suggests, instead of using option in the Preferences. That way, I can assign 'X' to cut the old way, and use another hotkey 'Shift-X' to do the 'mightypea cut'.
Using an option makes it hard to do both.
I haven't thought much about the consistency... maybe this is another thing, but shouldn't a tool's behaviour closer to what other major software is using? so users that come from other software feels don't get unexpected behavior :)
-
The chamfer tool selection was suggested by a user. What is your expected selection?
Well, it is not down to what do I expect, I am just looking for consistency.
Lets go back to the "Cut" tool for a moment.
As it is now, you have changed the defaults, added an option to change it back, and are looking at adding yet another option to change it again. That is just silly.
Lets look at a different way that is a consistent default, and rather than multiple hidden options to change default, have a single extra function.
For example with "Context Cut". The defaults could be to always have the sub_object pre-selection selected after the tool used. You then have a function that can select that new geometry created. That way, if you do not like the default, you can place the "Context_cut" into a "Composite Tool" and add the "Select new geometry" function.
-
How about I set the "Context Cut" tool to use the old behavior and "Context Cut(Break Edges)" to select new edges? That way there is no need to add a new tool or option.
-
i would just have tools select the best thing possible after use, that dosnt require the component mode to change.
Since what was bothering me, wasnt what was being selected, it was that the tool kept knocking me out of vertex mode.
-
How about I set the "Context Cut" tool to use the old behavior and "Context Cut(Break Edges)" to select new edges?
You certainly know how to miss the point.
Do as you will, it makes no difference to me.