This is good to know about but, similarly to Edwards suggestion, likely solves a different issue. Terry's suggestion with the otters example is exactly what I'm talking about.
On Tuesday, May 5, 2015 at 4:19:57 AM UTC-4, reinhard...@googlemail.com wrote: > > > > On Monday, May 4, 2015 at 1:14:47 PM UTC+2, john lunzer wrote: >> >> >> Could Leo have something like @int/@bool/@string/etc simple settings >> types but applicable to any node in an outline? >> >> Section references do what I'm talking about but in reverse. In a section >> reference you can reference blocks of code in a parent node and it will >> replace them if those section definition nodes are found as children. My >> proposal here is to have node which collects a type of node similar to >> section definition nodes where those definitions could be referenced >> anywhere in an outline (or suboutline) similarly to how simple settings >> nodes work. >> >> I guess I would call these *"Global Project Variables" if defined at the >> top level*. >> > > If you are working with Leo + Qt, you might try to use the global qApp > variable of Qt. > > With > > qApp.setProperty(myVariableName, myValue) > > and > > qApp.property(myVariableName) > > you can set and access any key-value pair globally. > It's not 'leonic', but maybe it solves your problem. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
