On Mon, Apr 27, 2009 at 9:47 PM, Graham Cox wrote:
> A road can be connected to other roads. Currently each road keeps a list of
> the "subroads" that are connected to it, which is a parent-child
> relationship. A parent road can have any number of child roads, but a child
> road can only have a m
On 28 Apr 2009, at 02:47, Graham Cox wrote:
Because of the cyclic nature of the network though, there isn't a
way I can see to simply sort the objects into the right order.
I snipped most of the above; anyone who cares to read it should refer
to the original message.
I think the crux of t
On 28/04/2009, at 11:47 AM, Graham Cox wrote:
Not directly a Cocoa question - apologies if that's inappropriate,
but I could do with some brain power to bear on this design problem
and there are lots of smart people here...
I have an object that represents a road, say. It has a path that
On Apr 27, 2009, at 9:47 PM, Graham Cox wrote:
Something tells me I'm missing a trick here. A data structure that
is intended to manage exactly this sort of interconnected network of
objects without the awkwardness I'm running into with this ad-hoc
approach. The problem is I don't know
Not directly a Cocoa question - apologies if that's inappropriate, but
I could do with some brain power to bear on this design problem and
there are lots of smart people here...
I have an object that represents a road, say. It has a path that gets
drawn to show the road. Typically there are
