Quick question, when I move two vertices to the same place, how do I easily join the seam?
do not move the vertices just
_stitch
the edges
you can also stitch vertices.
Edit:
and check
_reflect
and
_radiate
if you do symmetrical stuff like your images is showing
1 Like
Nice, that works well but I see a discrepancy in the workflow (@dale) that I think should be fixed:
When I run Stitch on two unjoined edges:
Then I can choose where in between them I want the joined vertex located, and hit Enter to get the center point. Great stuff, intuitive and fine.
But if the vertices area already correctly located before I use Stitch:
Then it is difficult to use Stitch, like if it is selecting the same edge twice or something.
(I see that I need to click on the different sides of the seam for it to select the correct ones)
So I don’t think it should be possible to select the same edge twice.
I see I can run stitch and select the same edge twice for both inputs on other naked edges too, so I think you need to remove the selected edges from the selection list for the command.
I also see that it is possible to select the same edge as part of the two sets and that causes an error: Invalid input for Stitch: (null)
But if I carefully select them on the correct sides of the already correctly positioned “seam” then it works fine and predictable.
The way I see it this would not happen if it wasn’t possible to select the same edge in both sets of inputs.
shift ctrl drag select the verts in that area instead of the edges. the command line should show the proper count (2 verts selected) then stitch to combine them into one- (enter, enter, to complete the command)
see video
2 Likes
Smooth, that’s my new friend now!
Still, the issue illustrated above still stands though, I think it should not be possible to select the same edge in both input sets 
But thank you for showing this, it will save me a lot of time. Up til now I have deleted faces and recreated them when I wasn’t able to stitch them. (That’s the problem of being an early adopter, you get bad habits, or don’t get good habits as the tools and documentation evolve 
)
you can shift ctrl drag select edges too…
you have to DESELECT the verts tho… or it all collapses to a singularity
Or just use a selection filter for just edges
I totally agree @Holo
my workaround:
in your case @Holo you do not need to select the inner edge… because they share a vert with the outer edge, when you stitch the outer edges, the inners become stitched by default.
see video
1 Like
This is what i love about Rhino, the underlying technology is always robust and intuitive 
But the user interface isn’t always polished enough to make the technology shine. So please give a response on the topic that an edge should not be possible to select in both edge sets.
@Holo , Sadly, I am not in a position to give an answer about why that is…I’m not a programmer, I’m an artist and a user/teacher (and smartass, amateur car restorer, household handyman and passible line cook) .
The best I can do is try to help others with tips on navigating the current state of the landscape.
I am more than happy to write up any issues that arise along the way and advocate for change, but in the end I’m at the mercy of the dev team just like you are.
so help me define the problem a little tighter-
the way I understand it, in a stitch operation, you want filtering to be applied so that one edge selected cannot be selected again in a 2nd selection set.
do I have that correct?
1 Like
Yes, spot on. That way users can pick rapidly and avoid wrongly picking the same edge twice if they are close to each other or at the same position.
stitch should be able to handle / repair situations like this:
_subDPlane 4x5
_unWeldEdge (3 inner edges)
above unwelded edges can be fixed with preselection.
but depend on the selection the result is correct or unexpected crap:
the 4th at the right is most crazy: selection filter subObjects, with points / vertices turned of.
cross selection
_stich will ask for a second set…
and what is also important:
the selection-process of similar commands should be the same
_blendSrf
_bridge
_stitch
… as soon as a closed edgeloop is selected, the selection of the second set should start.
as already wrote above - may workaround is to randomly move the first selection, than select than stitch to the unmoved / original part (“make it worse before stitch”)…
this will avoid unexpected behaviour / results
made worth (left)
stichted (right)
1 Like
got it- Will write this up.
fwiw my workaround fix for that is select those faces, delete, ,then bridge to put them back. or stich on set of verts at a time.
but I 100% get why you’d want to do this your way.
1 Like
I think Pascal did so in 2020 - See Youtrack RH-62027
1 Like
I just bumped this ticket back to life for v8
2 Likes
RH-62027 is fixed in Rhino 8 Service Release 16