Hi:
Im trying to use another outline from within the current outline.
Basically,the objective is to have another outline nodes and tree loaded as
virtual nodes so I can work with them from within the currently open
outline.
The thing is that several outlines use and edit those nodes, so
On 5/5/2014 6:56 AM, Fidel N wrote:
Hi:
Im trying to use another outline from within the current outline.
Basically,the objective is to have another outline nodes and tree
loaded as virtual nodes so I can work with them from within the
currently open outline.
The thing is that several
I think why Leo behaves as it does and how it should behave are
complicated by the problem of defining what Leo is.
Config. user friendliness wise I think there's a possible middle way
solution where we make the Leoine way easy for non-technical users.
I.e. a settings menu with a hierarchy that
Hey Jake, as said on the chat, big thanks. After playing with this I am
facing a problem that looks like a bug to me:
The new commander cant handle 'dc.all_unique_positions():' or any other
position generator function whatsoever.
Am I doing something wrong? Here is the code:
for com in
Ok, after the discussion on the chat, here is the solution (thanks for your
help everyone):
This script opens a Leo file, and traverses its nodes.
exists=0
for com in g.app.commanders():
if 'I_Programming.leo' in com.fileName():
dc = com
exists=1
break
if not
Thanks for the explanation, Terry.
I think the solution lies in the middle ground that you propose, and which
I was already looking forward to. But I thought it was going to be
implemented months ago! Things seem to have stalled, after an initial
flurry of activity (videocasts, etc) in the
On Mon, 5 May 2014 10:06:45 -0700 (PDT)
duf...@gmail.com wrote:
Thanks for the explanation, Terry.
I think the solution lies in the middle ground that you propose, and
which I was already looking forward to. But I thought it was going to
be implemented months ago! Things seem to have stalled,
