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 do crucial caching. Two different QTextEdit's or QDocument's might create the performance bug. 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 effectively disabling the cache. I don't know how much pyzo relies on it for speed, but a broken cache could certainly slow things down. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: ENB: pyzo syntax coloring: progress and a big mystery
'Terry Brown' via leo-editor Thu, 12 Jan 2017 07:18:07 -0800
- ENB: pyzo syntax coloring: progress and a big... Edward K. Ream
- Re: ENB: pyzo syntax coloring: progress ... Edward K. Ream
- Re: ENB: pyzo syntax coloring: progress ... 'Terry Brown' via leo-editor
- Re: ENB: pyzo syntax coloring: progr... Edward K. Ream
- Re: ENB: pyzo syntax coloring: p... john lunzer
- Re: ENB: pyzo syntax colorin... Edward K. Ream