Gulp! I guess I'm out of my depth on this one. I'll find something
easier to do!
Bob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to
On Tue, Apr 8, 2008 at 8:09 AM, bobjack [EMAIL PROTECTED] wrote:
Uhm... This looks more complicated than I thought. All the more reason
to encapsulate it and hide the details from plugins and scripts I suppose
...
Am I right in thinking
a) that stuff put on tnodes appears on all clones and
On Apr 8, 9:51 am, Edward K. Ream [EMAIL PROTECTED] wrote:
The question is, what does this mean :-) I think the short answer is that
the present scheme, involving descendentTnodeUnknownAttributes, does not
allow information contained in vnodes in @thin trees to be saved. However,
a plugin
On Apr 5, 3:06 pm, Terry Brown [EMAIL PROTECTED] wrote:
A comment on the term icon. Really to be clear we need to say
user-icon or status-icon. The status icon being the
content/clone/dirty/marked indicator that Leo's had for much longer
than it's had user-icons.
-x-cut-x-
I think the
On Mon, 7 Apr 2008 06:11:22 -0700 (PDT)
bobjack [EMAIL PROTECTED] wrote:
So maybe bobjack's high level container thing should have
status.marked, status.dirty, etc. attributes/methods, and while the
Tk interface uses an icon to show those, another interface might
not.
Sorry I'm
