On Wed, 30 May 2012 14:53:52 -0500 "Edward K. Ream" <[email protected]> wrote:
> This is a worthy bug. It smells strongly of an internal Qt bug, and I > think it will have to be debugged at the C-language level. > Considering the severity of the bug, I am seriously considering > waiving my "don't fix other people's bugs" rule. It may be time to > create a debugging build of Qt and dust off a C-language debugger. Before entering this dark, malodorous, and treacherous looking tunnel, might it be worth doing a bisection search through the last say 1000 Leo revs to see if there's a point where the problem first appears... ...that would be between 4654 and 4655. the changes there are certainly the right flavor to be causing this kind of trouble. 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.
