I wasn't planning on adding it too soon. Maybe in like two weeks
I'd get around to it. Edge selection isn't even my first
priority. The next changes I was planning to make, was put a bunch
of functions into the graphEltSet (the one that contains nodes +
edges). Functions such as: forAllVisibleNodes(Node n1, Node n2) or
forAllUniqueNodePairs( ""). The idea is that any time one
wanted to iterate through all the nodes, one would not have to access the
Node Vector directly, but instead would pass an object to the graphEltSet
containing such a function. (Kind of like Comparators in java
This would have allowed work on edge selection, and on making edges belong to nodes to be done in parallel.
Why do you ask? I hope it's because you actually want to try to implement this, in which case you have my green light. I probably won't do any coding till friday. (Supposedly I actually have a paying job, though I've been slacking).
At 06:36 AM 9/11/01 -0700, you wrote:
How soon you gonna add that code?
At 01:55 AM 9/11/2001 -0400, you wrote:
> >Looking at the tgLivingThing gif, one can begin to make the case that
> >Bernard did earlier: rollover popup of edge properties. That's tricky,
> >particularly with the curved edges -- will be tricky (methinks) to figure
> >out the bounding box for mouse detection. Worth a try, however.
>Nah-hah, that's the cool part. Curved edges do not pause a problem, and
>you know why? Because in terms of real coordinates, the edges are not
>curved. They just appear curved because they are warped by lenses.
>A formula for computing the distance from point (P) to a line (L) is
>simple, and it is also simple to find the point where a perpendicular line
>from P to L would cross L. So now, the only tricky part is converting back
>to visual coordinates, and determining when P is close enough to <P
>intersect L> to warrant an edge over trigger.
>Neat huh? And I guess that this feature can be implemented right now. For
>some reason, before, I thought that it would have to wait for edges to
>belong to nodes, rather then be out on their own. The other cool thing, is
>that once edges have mouse-over sensing, then one can implement all kinds
>of interfaces to manipulate them.... Drag from an edge to a node to switch
>endpoint? A scrollbar to change edge tension? Lots of things.
>Community email addresses:
> Post message: unrev-II@onelist.com
> Subscribe: unrev-IIemail@example.com
> Unsubscribe: unrev-IIfirstname.lastname@example.org
> List owner: unrev-IIemail@example.com
>Shortcut URL to this page:
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Yahoo! Groups Sponsor
Community email addresses:
Post message: unrev-II@onelist.com
List owner: unrev-IIfirstname.lastname@example.org
Shortcut URL to this page:
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
|Yahoo! Groups Sponsor|
This archive was generated by hypermail 2.0.0 : Tue Sep 11 2001 - 07:13:29 PDT