is there an assertion being triggered by the parser? I think I had to change the default qscintilla warning level down a level because occasionally a close to fatal assertion gets triggered splitting up strings. (sorry it was a couple of years ago so I'm a bit fuzzy.
-gedalia On Mon, Mar 19, 2012 at 9:29 PM, Jack Cosgrove <[email protected]>wrote: > Is there any way I can get some help with this? > > On Sat, 2012-03-17 at 12:58 -0500, Jack Cosgrove wrote: > > Hi, > > > > I am encountering crashes when I try to use autocomplete to fill in > > function arguments using the Python lexer. For example, given an API > > entry of "foo.bar(foo, bar)", I will always be prompted for foo and bar, > > but if I accept the autocompletion for "bar" and then type an opening > > parenthesis my app crashes. > > > > Attached is a small example demonstrating this behavior. Type in "fo", > > accept the suggestion, then ".", accept "bar", then "(" to replicate. > > > > However, if you type in "fo", accept, then ".bar(", then delete the "(", > > you can then type "(" again and encounter the function argument > > suggestion. After this happens the first time the application never > > crashes, even if replicating the first procedure on a new line. > > > > Thanks to all who reply for your help! > > > _______________________________________________ > QScintilla mailing list > [email protected] > http://www.riverbankcomputing.com/mailman/listinfo/qscintilla > -- --------------------------------------------------------------- cel: 917.776.8346 AIM: gedaliap http://www.gedalia.net --------------------------------------------------------------- Fight Entropy!!! Fight Entropy!!! Figth Etnropy! ! iFgth Etnrop!y ! giFth tErno!py ! giFt htrEno!p y! --- Well maybe not...
_______________________________________________ QScintilla mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/qscintilla
