Re: [Boa Constr] Segfault bugfix and "hello!"

[Riaan B. <riaan@e.co.za>]

Hello Shane,

Shane Hathaway wrote:

> I haven't looked at how Boa's debugger works, but IMHO it's always best to
> run a processing being debugged in a different process, especially
> considering that a lot of times what you need to debug is a segfault
> (GPF).

Boa's degugger is based on the IDLE debugger. It runs in the same
process as Boa.
I definitely agree that an out of process debugger is better, this is 
planned but so far I've not yet had the time to implement an IPC layer.
This should solve all the major gripes of the current debugger.

> 
> > I really hope someone with a little more debugger experience than me
> > would look into this.
> 
> I'm getting everything set up to start doing some work on Boa.  I think
> the debugger will be the first thing I'll look into.

I'll book in changes (including debugger updates) soon.
Good news, I'm now able to debug wxPython apps with Boa :)
Another significant drawback of in-process debugging is that modules
are only imported the first time. 

> > > Also, we need to find out why the editor is a bit sluggish.  I have
> > > identified and fixed a bug in Scintilla that makes it so Windows keyboard
> > > events are skipped,
> >
> > Which keys?
> > I had trouble binding ctrl with certain other keys e.g. '<', '>'
> 
> If the program spends too much time processing a keystroke, Windows will
> bunch the keystrokes into a single event.  Scintilla interprets the single
> event as a single keystorke, ignoring the repeat count.

Scintilla or wxStyledTextCtrl?
Please check this problem whenever you get your hands on the new
sources.

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net