it is probably not related. but today when coding with jr for a new version of blueprint we saw that it would be nice to have the possibility to share information either other all the packageBlueprints (we did that using a class) or between all the blueprints displayed inside a canvas. (this was for the color of the marked surfaces and knowing which one was selected). For the marked surface we took the easy road: we said ok the color table can be a class var and we will have one table for all the blueprint. Now for the selection (when we click on a bp head ) may be this is better to have the effect local to easel.
So what I want to say is that your annotations should be accessible from the scripts and it would be good to have - node - view - all nodes
Stef
Hi!
Now that some of you are building complex and interactive visualizations, I feel the need to add some annotations on things that are displayed. I am not talking about the model here, but really annotation on the view. For example, assume that I want the size of a node to increase (e.g., to see its method inside) when I double click on it. Where do I store the information that the node has been expanded ?
I started to have this need with popupView:. A node needs to know whether its popupview is on or not. I added a variable popup in MOGraphElement which solve this. But more complex interaction requires a generalization of this.
I am about to introduce a variable annotation in MOGraphElement that will lazily create a dictionary.
Any comment?
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev