A new 'slice' kind idea...

[Dimitri]

Paul, the initial loops may be defined easily by using the already existent 'plane cut' command...

[ggaliens]

Getting ready for the party ...

http://geomalgorithms.com/a05-_intersect-1.html

[puzzledpaul]

Paul, the initial loops may be defined easily by using the already existent 'plane cut' command...

Well, yes ... sort of - but Tools | Connect doesn't rely on element based loop definition procedures in the same way that Plane cut does, and thus often offers more versatility.

Since native wings tools for such things have been subjected to (wrongly, imo) derogatory comments - I was wondering / hoping that this feature might bring something new / better to the table.

pp

[Dimitri]

Paul, the 'connect' tool's workings has a dependency to the camera angle... and this make things very difficult to acquire accurate results by using it. Going back and forth to the camera-object align option too is very non practical and tiring. This exactly was reason that I did propose implementing a 'connect by shortest distance' command. I do understand well the objections existing as to the implementation of such a command... I know that it may have inaccuracies in some cases... but it is better having it for the cases that can work accurately then not having it at all.

Wings is in need of some retopo tools (or at least, some commands that would be an aid for retopologizing)... especially, now that it has so successfully working booleans. So, why not focusing on some such direction?

...

Mark, I do not know maths... I just try to conceive an idea by visual imagination. You are the expert in maths... so you have to 'translate' the tool propositions to the maths' language. I can offer my opinion only in the case I have visual explanations... : - )

[ggaliens]

Dimitri ... you must learn this much ...

SHEAF

I have written the code to find the implied sheaf point from two very flat objects. So I'm a good ways along.

[Dimitri]

'Finding the sheaf point from two flat objects'... it is near to what I said as an approach but it is not exactly the same thing... because the initial defining loops may not constitute necessarily a flat surface...

I am adding a new image below, illustrating the thing I am trying to say... as you see the loops, left and right, do not constitute a flat surface... so the 'sheaf' of flat surfaces concept can not apply to such a condition. Instead, the needed thing is having loops of equal distances between them arrayed in the space between the initial two loops...

[ggaliens]

Well ... there is probably no way I'm going to code the LOOP-MORPH you are suggesting. To complicated for me at this time. The loops I will sheaf will be flat-only. Sorry about that. Got to start with something.

[Dimitri]

No problem... do the 'sheaf' with the flat loops. It would be useful either. : - )

[puzzledpaul]

... the 'connect' tool's workings has a dependency to the camera angle... and this make things very difficult to acquire accurate results by using it. Going back and forth to the camera-object align option too is very non practical and tiring...

D - as you might suspect, I'm aware that Tools | Connect view is linked to camera angle - this has both pros and cons (imo)

As I mentioned a long time ago - on several occasions - also with examples of feature extensions - imo, modifying and improving what already exists - and works - should've been given greater consideration, rather than just adding supposedly 'better' stuff.

As regards alignment of an object to create the initial 2 datum loops for this proposed new feature being more difficult using T| C ... compared with Plane Cut ... I'd suggest the jury's still out ... because I'd bet that Plane cut is often going to be used with view xyz ... in which case, there's be no difference

Whilst I can see the point (and underlying agenda) behind this feature - my main issue is one of integration with existing tools.

pp

[ggaliens]

http://www.youtube.com/watch?v=HwZwKT7ecHM