Re: ENB: pyzo syntax coloring: progress and a big mystery

On Thu, Jan 12, 2017 at 12:37 PM, john lunzer wrote: > If you think you've hit a wall. I would not hesitate to contact Almar, he > has been extremely responsive to my questions in the past. > ​Thanks for this. It's good to know. But I haven't done my homework yet, and I

Re: ENB: pyzo syntax coloring: progress and a big mystery

If you think you've hit a wall. I would not hesitate to contact Almar, he has been extremely responsive to my questions in the past. On Thursday, January 12, 2017 at 11:39:26 AM UTC-5, Edward K. Ream wrote: > > On Thu, Jan 12, 2017 at 10:13 AM, 'Terry Brown' via leo-editor < >

Re: ENB: pyzo syntax coloring: progress and a big mystery

On Thu, Jan 12, 2017 at 10:13 AM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: ​> ​ Can you check that the cache is being hit, by reporting / counting hits? If it's never being used, or being asked to cache the same values repeatedly, then some communication issue must be

Re: ENB: pyzo syntax coloring: progress and a big mystery

2. Are the proper QDocument and QTextEdit being used? The present prototyping code uses an instance of pyzo's CodeEditorBase as way of instantiating the pyzo's syntax colorer.  Maybe the highlighter must be attached to Leo's actual QTextEdit body widget. The pyzo colorizer uses QDocument to

Re: ENB: pyzo syntax coloring: progress and a big mystery

On Thursday, January 12, 2017 at 9:05:03 AM UTC-5, Edward K. Ream wrote: > 1. How many times does PyzoHighlighter.highlightBlock get called? Adding a counter shows that this method is called once per line of the input file, as expected. So this is not the culprit. There is another way

ENB: pyzo syntax coloring: progress and a big mystery

Rev fbe428c shows the results of recent experiments using pyzo for syntax coloring in Leo. You could call this an Engineering Notebook post. You could also say that this discussion should be in #365 , but I wanted to make this discussion