The diff-marked-nodes command

I can't believe I could ever have lived without this command :-) It was sooo useful when merging VR and VR2 into VR3. It removes all the worry. The docstring: Create a node showing the diffs of two marked nodes. Clones of the marked nodes become the created node's children. *Notes*-

Re: ENB: Allowing (really) multiple viewrendered panes

On Thu, 31 Mar 2016 14:06:55 -0700 (PDT) "Edward K. Ream" wrote: > Another Engineering Notebook post. Feel free to ignore unless you > are Terry or > Peter Mills. > > While merging VR and VR2, it has become clear that the present > approach to having multiple VR panes has

Re: An important new Leonine pattern for docstrings

On Thu, 31 Mar 2016 14:19:42 -0700 (PDT) "Edward K. Ream" wrote: > The only drawback is that the actual external file contains sentinel > lines separating the parts of the docstring. In practice, it's no > big deal, especially if each child starts with a blank line. Might

An important new Leonine pattern for docstrings

One of the benefits of getting into a methodical mood is that little annoyances become intolerable. While working on the VR3 plugin, I wanted to compare docstrings as well as code. In the process, the following pattern emerged. 1. @file viewrendered.py now starts off as follows: ''' << vr3

ENB: Allowing (really) multiple viewrendered panes

Another Engineering Notebook post. Feel free to ignore unless you are Terry or Peter Mills. While merging VR and VR2, it has become clear that the present approach to having multiple VR panes has *no chance* of working. Indeed, there is a global *controllers *dict, but the keys are

ENB: Merging VR and VR2 into VR3

After three or four failed attempts, I have finally hit upon a, safe, methodical strategy that should be guaranteed to work. You can call this an Engineering Notebook post. Only those directly involved in the viewrendered plugins need take note. *A methodical approach* 1. viewrendered.py

The merger of VR and VR2 will be VR3

As a practical matter, it's not good to be messing around with either "base", so I'll be creating viewrendered3.py soon. This will be guaranteed to be broken until I announce otherwise. Feel free to revert either VR or VR2 to any previous state. I won't care, as I'll be using my own copies

Re: d614f5a: Improved initial directories in open/save dialogs

That will be a nice improvement, thanks! Rob.. On Thursday, March 31, 2016 at 6:59:22 AM UTC-4, Edward K. Ream wrote: > > This request has been around for a long time > . > > If the selected node is an @ node, or

Re: MD or RST?

On Mon, Mar 28, 2016 at 5:51 AM, Peter Mills wrote: > In summary, I’d suggest (depending on how well VR2 has kept up with VR’s > updates) that VR2 is essentially a superset of VR functionality, and should > become the *only* VR plugin. > ​I agree, but this is far from

d614f5a: Improved initial directories in open/save dialogs

This request has been around for a long time . If the selected node is an @ node, or descendant of same, the initial directory will be the directory to which the tree will be saved. Otherwise, c.last_dir will be used if it

Re: Click links not working

On Wed, Mar 30, 2016 at 9:34 PM, Largo84 wrote: > Not sure if these issues are related, but they seemed to coincide with > recent Github pulls. > ​Sorry about that. Fixed at 9d3721. The problem is a perennial confusion between the old QtGui module and the newer QtWidgets

Re: Click links not working

click on links is still working for me. *My Leo Log Window* *Leo 5.3-devel, build 20160329092115, Tue Mar 29 09:21:15 CDT 2016* *Git repo info: branch = master, commit = a43f668dedb0* *Python 2.7.11, PyQt version 4.8.7* *Windows 7 AMD64 (build 6.1.7601) SP1* I'll try the latest build soon.

Re: Click links not working

On Thursday, March 31, 2016 at 3:34:12 AM UTC+1, Largo84 wrote: > > Not sure if these issues are related, but they seemed to coincide with > recent Github pulls. > > 1) Click links no longer triggers the link to open. I can still use > the Open URL command in the header right-click menu.