Moin, On Tuesday 24 August 2010 11:42:19 Zoltan Padrah wrote: > As implementing the simulator, I've found a problem with the IDocumentModel > interface: it doesn't expose the set of nodes, that don't belong to any > component/element. This is a problem, because those nodes are needed by the > connectors is some cases. When two connectors are connected, a new node is > created at the connection point, and one connector is split in two, finally > resulting in three connectors and one node. This way, in the model, a > connector can always connect two nodes. Yes, I’m facing this situation, too. So I would be fine with exposing this information from the IDocumentModel and sync to it, everytime something changes.
> As I've seen in the CircuitModel class, the nodes had to be inserted in > that class, too. It’s no problem to move this information one level higher into IDocumentModel. > Theoretically it's possible to deduce all nodes from the end-node-id-s of > the connectors, but I'm not sure if that is the best solution. agreed! > So should be the nodes exposed in IDocumentModel, or not? What is your > opinion? +1 from me bye then julian
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________ Ktechlab-devel mailing list Ktechlab-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ktechlab-devel
