Re: Matt, what's the status of #562?

8b6f281 puts the Pypi build and upload notes into nodes. The "Matt's workflow for updating pypi" node can be deleted. I delayed doing so as I'm not sure we're finished with it? On Sun, Jan 28, 2018 at

Re: Matt, what's the status of #562?

Thanks for picking this up and pointing out the bits that aren't clear. > Is it really true, as you imply, that pyqt gets installed automatically with python 3? Or have I misunderstood something? Yes that's correct. There is a pypi PyQt wheel for py3.4+ but not for py2.7+. > - I have punted on

Re: When using LeoBridge, leoG.IdleTime() always returns None

On 01/28/2018 01:45 AM, Edward K. Ream wrote: > This may allow you to test your code, /provided/ you don't expect > anything to happen at idle time. Leo-Babel needs leoG.IdleTime() to function correctly in order to for Leo-Babel to function correctly. Same for the code used to test Leo-Babel.

Re: When using LeoBridge, leoG.IdleTime() always returns None

On 01/28/2018 01:53 AM, Edward K. Ream wrote: > Perhaps a subclass of g.IdleTime would make this easier, say by > registering itself with the script. I'm not sure what you mean. I will probably try monkey patching g.IdleTime before calling LeoBridge. That is, I will try implementing an idle

Re: New plugin line_numbering

Hi: I'm running the latest Leo from Git. I just enabled this plugin. With "nosent" files (at least, since that's mostly what I use), there seems to be an "off-by-a-few" error in the displayed numbers. My outline is: @nosent foo.py @others (in body of @nosent node) Imports import xx

Rev 145f074: new "exact" keyword arg to g.findNode* methods

Rev 145f074 adds the exact=True keyword argument to g.findNodeInChildren, g.findNodeInTree, and g.findNodeAnywhere. The default ensures current behavior does not change. All three methods first look for an exact match, regardless of the exact keyword, just as before. If no match is found, and

Re: d0c4a8e: Simpler way to use the demo.py plugin

On Sunday, January 28, 2018 at 5:37:01 AM UTC-6, Edward K. Ream wrote: *Summary* > > The new pattern is an important simplification for non-interactive > scripts. Such scripts will wait for predetermined times between "slides". > > The old pattern is more flexible for interactive demos. It

d0c4a8e: Simpler way to use the demo.py plugin

In a roundabout way I was inspired by the 3Blue1Brown YouTube channel. It uses the manim library to do animations. But the real reason for the Aha was that I had forgotten how to use demo.py.

Re: When using LeoBridge, leoG.IdleTime() always returns None

On Sun, Jan 28, 2018 at 3:45 AM, Edward K. Ream wrote: There is no such thing as "idle time" in the bridge. Instead, there is > just a script that is run from "start to finish". > ​There is no event loop in the bridge. NullGui.runMainLoop does exist, but it isn't called

Re: When using LeoBridge, leoG.IdleTime() always returns None

On Sat, Jan 27, 2018 at 3:44 PM, SegundoBob wrote: ​​ > g.app.gui.idleTimeClass is None so leoG.IdleTime() always returns None. > > Is this a recognized limitation? > ​It is now ;-) ​ > Is this limitation necessary? > ​A good question. There is no such thing as "idle