This was an amazing "conclusion" to these events. I too want to take the
opportunity to apologize to Edward for accusations, implied or explicit. I
learned from this series of interactions and it appears Vitalije has as
well. Edward, it is my hope that you can take something good away from
>
>
> Great help in quickly traversing tree to the given top position is to now
>> how many nodes are in its subtree. In my model it is the size of a node.
>>
>
> True, but the big payoff will come from just drawing/allocating
> approximately N nodes, where there are N visible nodes in the
On Wednesday, August 8, 2018 at 1:10:16 PM UTC-5, vitalije wrote:
Your recent posts in other thread have opened my eyes and I was planing to
> encourage you to go and do this issue yourself in your own way.
>
Thank you. It is a big relief to me.
In our previous discussions and disagreements
On Thursday, August 9, 2018 at 11:22:39 AM UTC+1, john lunzer wrote:
>
> This was an amazing "conclusion" to these events. I too want to take the
> opportunity to apologize to Edward for accusations, implied or explicit. I
> learned from this series of interactions and it appears Vitalije has
On Thu, Aug 9, 2018 at 10:26 AM, jkn wrote:
What a hearteningly grown-up place this part of the internet is! I too
> would like to thank both Vitalije and Edward for the tone of their
> 'sparring' in recent weeks.
>
You're welcome. It is becoming clear that we humans have tolerated far too
On Thu, Aug 9, 2018 at 7:57 AM, vitalije wrote:
What I meant is that it can help to calculate the top_position.
>
Yes. This is a surprisingly interesting and subtle task. There are
important, design choices involved. Most users will be only subliminally
aware of those choices.
For example, a
On Thu, 9 Aug 2018 21:59:47 -0500
"Edward K. Ream" wrote:
> On Thu, Aug 9, 2018 at 6:46 PM, Terry Brown
> wrote:
>
>File
> "/mnt/usr1/tnb_data/Package/leo/git/leo-editor/leo/core/leoFileCommands.py",
> > line 416, in getLeoOutlineFromClipboardRetainingClones
> > assert c.hiddenRootNode
On Thu, Aug 9, 2018 at 7:57 AM, vitalije wrote:
>
>> Great help in quickly traversing tree to the given top position is to now
>>> how many nodes are in its subtree. In my model it is the size of a node.
>>>
>>
This turns out to be more important than I first thought. If the code is to
set
On Thu, 9 Aug 2018 11:01:17 -0500
"Edward K. Ream" wrote:
> Another quick experiment shows that Terry's Easter Egg interface does
> not, at present, support any graphics pane.
Not quite sure what you mean. The free_layout / NestedSplitter
machinery (which I'd like to replace with the QDock
On Thu, 9 Aug 2018 12:19:45 -0500
"Edward K. Ream" wrote:
> > Not quite sure what you mean. The free_layout / NestedSplitter
> > machinery (which I'd like to replace with the QDock layout scheme)
> > should be able to host any Qt Widget. But it doesn't *provide*
> > *any*, graphics pane or
I wanted to create an outline that looks like this:
O
A
B
C
D
E
A
B
C
where A is a clone. So when I Shift-Control-C copied A and then tried
Outline -> Paste as Clone with E selected, I got:
File
"/mnt/usr1/tnb_data/Package/leo/git/leo-editor/leo/core/leoFileCommands.py",
On Thursday, August 9, 2018 at 12:33:18 PM UTC-5, Edward K. Ream wrote:
>
> On Thu, Aug 9, 2018 at 7:57 AM, vitalije wrote:
>
>>
>>> Great help in quickly traversing tree to the given top position is to
now how many nodes are in its subtree. In my model it is the size of a
node.
On Thu, Aug 9, 2018 at 2:32 PM, Edward K. Ream wrote:
> The [countPrevVisible] method uses an inlined version of
p.moveToVisNext():
The fast-draw branch is ready for serious testing!
It is much faster than the code in "devel", without changing very much.
This is completely unexpected.
On Thu, Aug 9, 2018 at 6:43 PM, Edward K. Ream wrote:
P. S.
> At present the expand-all command causes the vertical scroll bars to
> disappear.
>
Actually, the "thumb" exists, but is tiny.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor"
14 matches
Mail list logo