[Gambas-devel] Aktivating editor-windows in IDE

[Charlie Reinl]

Am Mittwoch, den 27.12.2006, 00:21 +0100 schrieb Benoit Minisini: 
> On Wednesday 27 December 2006 00:07, Charlie Reinl wrote:
> > Salut Benoît,
> >
> > what I wana to is, to unset/set  Breakpoints from FDebugInfo.lstBreak by a
> > dblclick.
> >
> > In my testing IDE that works fine.
> >
> > My problem is to switch back to the editor-windows, which where open when I
> > dblclicked.
> >
> > FDebugInfo.lstBreak is a ColumnView in my IDE/FDebugInfo.form now.
> >
> >   sLastLine = lstStack[0].Text
> >
> > --- some code to set/unset the breakpoint, which works
> >
> >     xArgs = Scan(sLastLine, "*.*.*")
> >     hWin = Project.OpenFile(Project.FindPath(CStr(xArgs[0])),
> > CInt(xArgs[2]))
> >
> > switchs back to that editor-window,
> > but the editor-window is grey (not enabled) and the only way I found, was
> > to set the ReadOnly of that editor-window to TRUE.
> > But that cause problems, I can't close that project no more after.
> >
> > Do you have any hint for me ?
> >
> > Amicalment
> > Charlie
> >
> 
> While debugging, every editor window is read-only.
> 
> Anyway, breakpoint management is now a full mess: there are functions for 
> setting, toggling breakpoints everywhere. You made a "clear all breakpoints" 
> functions, whereas this function already exists in FDebugInfo. And so on...
> 
> Things must be redone cleanly: I will do that by putting everything in the 
> Design module. I think I will put all breakpoints in a string array.
> 
> Regards,
> 
Let me explain my idea behind : 
	short := comfort

longer : = 

- The added 'clear all breakpoints' is to have the possibility to do
that, if the FDebugInfo window is not yet available, means before
starting to debug.

- The new possibility to switch on/off the breakpoints in
FDebugInfo.lstBreak is to have an easy way to stop or not in the next
step. 
e.g. you loop , in that loop a function is called, where a breakpoint is
set, but you only want to see if that function is called with the value
'toto' 

In FDebugInfo.lstBreak when you start to debug, you see all the set
breakpoints with an Check-Icon.
If you dblclick the Icon change to UnChecked, the breakpoint is set to
False (stripped) but the entry for that breakpoint keeps staying in 
FDebugInfo.lstBreak.

So if the value in example is 'toto' you can switch on the breakpoint by
an simple dblclick.

Amicalment
Charlie