Re: [Dltk-dev] toggle class/global variables actions

[Andrei Sobolev <andrei.sobolev@xxxxxxxxx>]

Hi Jae,
> hello all -
>
>   quick question, i was wondering why the toggle class/global variable
> actions were implemented by changing the preference value (which
> causes the engine to re-update the stack frame using the new settings)
> instead of just filtering the results out of the view.
Because it could be very slow to get all variables.
>  
>   i'm working on adding the support for language/project specific
> debugging engine options and it seems the implementation would be
> simpler (and allow more of it to exist in the core dltk) if the
> results could be filtered instead of flipping the preference value. it
> would also be a lot simpler if the engine settings only applied to the
> next launch, instead of one that was potentially already in progress.
> since the 'break on first line'  and 'enable logging' only apply to
> launch, i would think that would apply to the other options as well.
> it would also save multiple round trips to the engine if the user
> wanted to flip things on and off.
>
>   thoughts?
Yes, you are right, some options are used only in launch.
I suppose we could move some them from generic dltk settings to launch
configurations ("break on first line" for example).

Best regards,
Andrei Sobolev.