On Thu, Mar 19, 2015 at 2:58 PM, Largo84 wrote:
> This is great and very helpful.
>
Glad you like it.
> Not sure if this is an error or simply not understanding something on my
> part. The following is on the website:
>
> extract-names (Ctrl-Shift-Command)
> I don't have a 'Command' key so
This is great and very helpful. Not sure if this is an error or simply not
understanding something on my part. The following is on the website:
extract-names (Ctrl-Shift-Command)
I don't have a 'Command' key so I looked in the menu and on my Win7 PC, the
menu suggests Ctrl-Shift-N
Rob..
That would be a great help to link to other references (like Emacs or Vim)
that use similar terminology and solve similar problems. No sense in
'reinventing the wheel'.
Rob..
On Thursday, March 19, 2015 at 11:00:49 AM UTC-4, Edward K. Ream wrote:
>
>
>
> On Mon, Mar 16, 2015 at 4:35
On Thu, 19 Mar 2015 10:09:51 -0500
"Edward K. Ream" wrote:
> Terry, could you track this down please?
TL;DR: delete all the iconclick* entries from the table at:
http://leoeditor.com/scripting.html#event-handlers
I think the iconclick* handlers are all dead, because clicking the icon
part of a
On Thursday, March 19, 2015 at 10:26:37 AM UTC-5, Edward K. Ream wrote:
>
> On Thursday, March 19, 2015 at 5:55:09 AM UTC-5, Edward K. Ream wrote:
>
> > Imo, nobody would notice if Leo *always* checked the .leo file after
> reading and before writing. Except when the checks prevented catastrophe :
On Thursday, March 19, 2015 at 5:55:09 AM UTC-5, Edward K. Ream wrote:
> Imo, nobody would notice if Leo *always* checked the .leo file after
reading and before writing. Except when the checks prevented catastrophe :-)
If I don't hear from anyone today I'll put this in tomorrow.
EKR
--
You re
On Tue, Mar 17, 2015 at 11:39 AM, 'Terry Brown' via leo-editor <
leo-editor@googlegroups.com> wrote:
>
Interesting coincidence that I just tweaked quickMove.py to operate on
multiple nodes.
[snip]
> One important concept is that multi-node selection still has a
single 'current' node, typi
On Thu, Mar 19, 2015 at 10:01 AM, Jacob M. Peck
wrote:
> On 3/19/2015 10:40 AM, Edward K. Ream wrote:
>
>> - c.cleo doesn't exist because, iirc, cleo was a tk plugin.
>>
> I'm fairly certain that todo.py creates c.cleo. That's how I access
> todo.py's functionality from scripts. Not sure why th
On Thu, 19 Mar 2015 09:40:11 -0500
"Edward K. Ream" wrote:
> - 'headclick2' is matched with 'headdclick1' (missing d in headclick2)
headclick hook names changed some time back, I think the table's
correct now though.
> - c.cleo doesn't exist because, iirc, cleo was a tk plugin.
For hysterica
On 3/19/2015 10:40 AM, Edward K. Ream wrote:
- c.cleo doesn't exist because, iirc, cleo was a tk plugin.
I'm fairly certain that todo.py creates c.cleo. That's how I access
todo.py's functionality from scripts. Not sure why the loading order
would cause that creation to fail, though.
-->Jak
On Mon, Mar 16, 2015 at 4:35 PM, 'Terry Brown' via leo-editor
wrote:
> On Mon, 16 Mar 2015 14:18:23 -0700 (PDT)
> Largo84 wrote:
>
> > I'm really glad the docs are being updated. I know that's a
> > monumental task. I only use a fraction of Leo's commands, mostly
> > because I don't even know w
On Mon, Mar 16, 2015 at 9:00 AM, 'Terry Brown' via leo-editor <
leo-editor@googlegroups.com> wrote:
> ...instead of just the current node.
>
Thanks for this. I don't see any changes to the docstring in the git log
;-) Imo, the docstring is the place to document new feature. Users can
see it b
On Tue, Mar 10, 2015 at 10:24 AM, 'Terry Brown' via leo-editor <
leo-editor@googlegroups.com> wrote:
> START: GIS gobbledegook
> QGis somehow fails to read the projection information from a .tif even
> though gdalinfo can read it, so I'm thinking there must be an easy way
> to create a separate wo
On Tue, Mar 17, 2015 at 12:47 PM, john lunzer wrote:
> Here are my findings, *I did most of my testing with ONLY my plugin
> enabled*:
>
> The relevant code from leo\plugins\qt_tree.py:
>
> def onIconBoxDoubleClick (self,event,p=None):
> if self.busy(): return
>
> c = self.c
>
Checking the outline after reads and before write takes a negligible amount
of time. On my mid-range machine it takes 0.15 sec. per 10,000 nodes. That
is, about 0.10 sec. on leoPy.leo.
Imo, nobody would notice if Leo *always* checked the .leo file after
reading and before writing. Except when
15 matches
Mail list logo
