See NSView's hitTest: method. I believe you'll also have to use one
or more of NSView's convertPoint... methods.
Stepping back a bit, if you intend to significantly grow your app you
should give it an MVC architecture -- have a model class that
represents the structure and content of your
On Mon, Feb 23, 2009 at 8:45 AM, Manuel Meyer wrote:
> Hmm, the endPoint and startingPoint are just helpers right now to visualize
> the mouse interaction. I haven't done any coding on the vertices between two
> Nodes yet.
> I wanted to connect the Nodes without using the superview, but maybe I ha
Hmm, the endPoint and startingPoint are just helpers right now to
visualize the mouse interaction. I haven't done any coding on the
vertices between two Nodes yet.
I wanted to connect the Nodes without using the superview, but maybe I
have to? What is the best way to find out, what View(s) ar
I'm not sure there is a problem. If the clicked NodeView is receiving
all the rightMouseDragged: messages, even when the mouse leaves the
view, it would be consistent for it to receive the rightMouseUp:
message as well. Note that at the time the user releases the mouse,
it might not be ov
Hey,
I just started to learn obj-c/Cocoa. As my first application I am
writing a networkgraph-editor. Each node got it own view.
To connect to nodes, I thought of using rightMouseDown,
rightMouseDragged and rightMouseUp.
So the NodeView, where a rightMouseDown event is triggered will be the
