> Every node has a python dictionary associated with it which can be > accessed as p.u (I think?) or v.u (certainly) when you're scripting > Leo, a lot of plugins use it to store info. they need, like icons for a > node, color of a node, etc. The dictionary is saved in the .leo file, > so it's a very useful feature for scripting. Historically the > dictionary has been called as "unknown attributes", meaning things not > known to Leo's core, hence uA.
So, perhaps User Attributes would work also, or are some of these attributes already de-facto standards (e.g. icon, color etc). In the latter case it would be imperative, that these get documented in a central place. Perhaps node attributes would be a better name. I tried: g.es(p.u) and get 'position' object has no attribute 'u' I tried also: g.es(v.u) and get name 'v' is not defined. This works: g.es(p.v.u) What is v? Is this the unique node, which is identical when multiple p represent the same clone? - Josef -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
