Re: A prototype of fast Qt tree drawing

On Fri, 10 Aug 2018 11:06:11 -0700 (PDT) "Edward K. Ream" wrote: > On Thursday, August 9, 2018 at 12:50:20 PM UTC-5, Terry Brown wrote: > > > But for the sake of completeness, here's a turtle: > > I can set up the new pane, and run the script. Traces show: Hmm, it worked for me, drew a stair

Re: A prototype of fast Qt tree drawing

On Thursday, August 9, 2018 at 12:50:20 PM UTC-5, Terry Brown wrote: > But for the sake of completeness, here's a turtle: I can set up the new pane, and run the script. Traces show: turtle_run 0 0 160 0 turtle_run 160 0 160.0 80.0 turtle_run 160.0 80.0 200.0 80.0 turtle_run 200.0 80.0 200.0

Re: A prototype of fast Qt tree drawing

On Friday, August 10, 2018 at 4:17:55 AM UTC-5, Edward K. Ream wrote: > > On Fri, Aug 10, 2018 at 1:05 AM, vitalije wrote: > > I hope fast-draw will be soon merged in devel. >> > > I am seeing some bad behavior re clones at present. > The fast-draw2 branch seems to fix all the obvious problems.

Re: A prototype of fast Qt tree drawing

On Fri, Aug 10, 2018 at 1:05 AM, vitalije wrote: I hope fast-draw will be soon merged in devel. > I am seeing some bad behavior re clones at present. I'm not sure this is related to Terry's clone issue, but it needs thorough exploration before fast-draw is ready for prime time. Edward --

Re: A prototype of fast Qt tree drawing

I am glad that your work resulted in such improvements so quick. > P. S. >> At present the expand-all command causes the vertical scroll bars to >> disappear. >> > > Actually, the "thumb" exists, but is tiny. > > Yes, I noticed this too. When the tree is very large and fully expanded it

Re: A prototype of fast Qt tree drawing

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"

Re: A prototype of fast Qt tree drawing

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.

Re: A prototype of fast Qt tree drawing

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.

Re: A prototype of fast Qt tree drawing

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

Re: A prototype of fast Qt tree drawing

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

Re: A prototype of fast Qt tree drawing

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

Re: A prototype of fast Qt tree drawing

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

Re: A prototype of fast Qt tree drawing

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

Re: A prototype of fast Qt tree drawing

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

Re: A prototype of fast Qt tree drawing

> > > 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

Re: A prototype of fast Qt tree drawing

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

Re: A prototype of fast Qt tree drawing

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

Re: A prototype of fast Qt tree drawing

I am glad that you started to work on this issue. 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. In our previous discussions and disagreements I misjudge you. I was at some points annoyed by your

A prototype of fast Qt tree drawing

The new code is mostly in qtree.partialDraw, in the "quick-draw" branch. The new code is a prototype of #942 . I do *not* plan much more work on it. I just wanted to explore some ideas to so I could stop thinking about them. The code draws