On Sat, 29 May 2010 19:46:58 +0100, Baz Walter <[email protected]> wrote: > On 29/05/10 17:37, Baz Walter wrote: >> On 29/05/10 10:00, Phil Thompson wrote: >>> Fixed in the current PyQt snapshot - sort of. It assumes that the char * >>> refers to a '\0' terminated string, which may not be the case. >>> >>> Although earlier versions didn't seem to crash, I don't think they >>> worked >>> any better. >> >> thanks phil >> >> i've tried the new pyqt snapshot with the latest qscintilla snapshot. i >> tested all the scintilla notifications that send char * (SCN_MODIFIED, >> SCN_USERLISTSELECTION and SCN_AUTOCSELECTION) and none of them now >> produce errors or crashes. > > looks like i spoke too soon: i now get segfaults when trying to emit > signals that send char *. > > the particular signal that caused the crash was "propertyChanged(const > char *prop, const char *val)" in QsciLexer. i have been using this > signal for a long time previously without any problems.
Should be fixed in tonight's PyQt snapshot. You will also need tonight's QScintilla snapshot. SCN_MODIFIED should now provide a more sensible text argument. Phil _______________________________________________ PyQt mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/pyqt
