On Wed, 30 May 2012 04:28:04 -0500 "Edward K. Ream" <[email protected]> wrote:
> So the question is, is there some way to correct the clipping region > created by QSyntaxHighlighter.rehighlight? If so, then a call to > w.update would presumably make everything right. I don't have Qt installed for Py 3 here at work, so I can't test this, but to me it didn't really seem like a clipping problem at all. I was seeing the line simply not displayed at all - I saw this with the bug the first time, and again yesterday - you could mouse-wheel down to show the lines below the missing line, and move the text cursor above and below the missing line with the cursor keys. When the cursor was on the missing line the cursor would disappear, an additional arrow-down would make it reappear on the next line. I think the line numbers updated correctly. So basically the behavior was exactly as if the line was being displayed zero pixels high, lines before and after were shown ok. I'm not familiar with all the details so maybe this is clipping related somehow, but to me it's more a question of a bad colorizer / display tag on that line, as subsequent lines were visible. Almost like a carriage return without a line feed :-} Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
