Split Edge Selection

[Timothy M. Shead]

Joe:

Seems like we've discussed this in the past, but I can't find it in the
wiki ... what are your preferences on the following:

* When picking edges, do we automatically pick both split edges, pick
one, or provide an option?  Assuming an option, what's the default?

* When rendering edges, how should individual split edge selections be
represented?  Currently we ignore this issue, the visual appearance is
the same whether you select one split edge or both.

Cheers,
Tim


[tshead.vcf]

---

begin:vcard
fn:Timothy Shead
n:Shead;Timothy
org:www.k-3d.org
email;internet:tshead@...
title:Founder
x-mozilla-html:FALSE
version:2.1
end:vcard

---

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development

[Joe Crawford]

On Tue, Aug 25, 2009 at 10:12 PM, Timothy M. Shead<tshead@...> wrote:
> Joe:
>
> Seems like we've discussed this in the past, but I can't find it in the wiki
> ... what are your preferences on the following:

Ok, I will answer first, but then mention some more general thoughts I
have on the matter.

> * When picking edges, do we automatically pick both split edges, pick one,
> or provide an option?  Assuming an option, what's the default?

I think we should automatically pick both, but this should only be
considered as one selected edge. From a users perspective, there is
only one edge.  Anything in the UI that says how many edges are
selected should say "1".

There should be an option, for another selection mode.

> * When rendering edges, how should individual split edge selections be
> represented?  Currently we ignore this issue, the visual appearance is the
> same whether you select one split edge or both.

Maya uses a trick where when selecting face varying data, it breaks
apart every face, rendering each one a little bit smaller than it
really is, so there are tiny gaps in between each face. Then the
selections of face varying data are more clear. This takes care of
both seeing what is selected, and also having two seperate targets to
click on.

To me, individual edge "sides" are basically another kind of face
varying data. Perhaps we call them "face edges" or we call them
"edgesides". They need a name.

In any case, we need clear terminology.  To stay consistent with the
rest of the 3d world, an edge needs to be a single thing, made up of
two other things called something else. (in k3d, I suppose that means
that one edge itself is made of two "edgesides").


Sincerely,

Joe Crawford
___________________________________
Owner - Celestine Studios   and   Joetainment Enterprises
Cell: 604-866-3050
Email: joetainment@...
Web: http://celestinestudios.com

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development

[bART Janssens-2]

On Thu, Aug 27, 2009 at 10:02 PM, Joe Crawford<joetainment@...> wrote:
> To me, individual edge "sides" are basically another kind of face
> varying data. Perhaps we call them "face edges" or we call them
> "edgesides". They need a name.

I would suggest "halfedge" here. It's from the formal descriptions of
such datastructures, but it encapsulates the idea pretty well.

Cheers,

--
Bart

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development

[Joe Crawford]

> I would suggest "halfedge" here. It's from the formal descriptions of
> such datastructures, but it encapsulates the idea pretty well.

I like that.  If it matches some kind of formal description, and still
makes sense, then it is our best bet.

Sincerely,

Joe Crawford
___________________________________
Owner - Celestine Studios   and   Joetainment Enterprises
Cell: 604-866-3050
Email: joetainment@...
Web: http://celestinestudios.com

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development

[Timothy M. Shead]

Joe Crawford wrote:
>> I would suggest "halfedge" here. It's from the formal descriptions of
>> such datastructures, but it encapsulates the idea pretty well.
>
> I like that.  If it matches some kind of formal description, and still
> makes sense, then it is our best bet.

I'm pretty sure this doesn't come up in the UI at all, but "half edge"
it is.

Cheers,
Tim

[tshead.vcf]

---

begin:vcard
fn:Timothy Shead
n:Shead;Timothy
org:www.k-3d.org
email;internet:tshead@...
title:Founder
x-mozilla-html:FALSE
version:2.1
end:vcard

---

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development

[Joe Crawford]

On Tue, Sep 1, 2009 at 7:34 AM, Timothy M. Shead<tshead@...> wrote:

> Joe Crawford wrote:
>>>
>>> I would suggest "halfedge" here. It's from the formal descriptions of
>>> such datastructures, but it encapsulates the idea pretty well.
>>
>> I like that.  If it matches some kind of formal description, and still
>> makes sense, then it is our best bet.
>
> I'm pretty sure this doesn't come up in the UI at all, but "half edge" it
> is.

I think the main point right now is that is does eventually need to
come up in the UI.  In the UI, we should always use edge to mean a
single thing/structure defined by two halfedges, and whenever we need
to select a single side of an edges, we need to always refer to that
as a half edge.  This should fully make sense to both technically
minded people, and less technical artists.


Sincerely,

Joe Crawford
___________________________________
Owner - Celestine Studios   and   Joetainment Enterprises
Cell: 604-866-3050
Email: joetainment@...
Web: http://celestinestudios.com

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development