Juergen Vigna wrote:
> Andre Poenitz wrote:
>> I am starting to believe that all insets should cache a bufferview
>> or some "context" after e.g. draw() is called ...
>
> The problem with this is that the BufferView is sometimes redone and
> you point to a non valid pointer (the problems we had e
Andre Poenitz wrote:
I am starting to believe that all insets should cache a bufferview or some
"context" after e.g. draw() is called ...
The problem with this is that the BufferView is sometimes redone and
you point to a non valid pointer (the problems we had especially in
the beginning with In
On Tue, 18 Feb 2003, Andre Poenitz wrote:
> On Tue, Feb 18, 2003 at 02:44:11PM +, Angus Leeming wrote:
> > I think I have just about cleaned up the controllers code so that it is now
> > transparent. As a result of this clean-up I have managed to replace all
> > those boost::signals in fronten
Andre Poenitz wrote:
>> The only problem that remains is extracting the cached_bufferview (which
>> is a problem common to all these 'solutions').
>
> I am starting to believe that all insets should cache a bufferview or some
> "context" after e.g. draw() is called ...
>
>> Am I correct in saying
On Tue, Feb 18, 2003 at 03:15:21PM +, Angus Leeming wrote:
> Andre Poenitz wrote:
> > Not sure. I personally would lean to the first option, as the InsetBase
> > ideally does not know anything about dialogs
> >
> > (which, of course is not true, as it has to declase 'hideDialog'...).
>
> Not
Andre Poenitz wrote:
> Not sure. I personally would lean to the first option, as the InsetBase
> ideally does not know anything about dialogs
>
> (which, of course is not true, as it has to declase 'hideDialog'...).
Not true. hideDialog need not be virtual if we adopt your 'guiding
principle', a
On Tue, Feb 18, 2003 at 02:44:11PM +, Angus Leeming wrote:
> I think I have just about cleaned up the controllers code so that it is now
> transparent. As a result of this clean-up I have managed to replace all
> those boost::signals in frontends/Dialogs.h with normal C++ class methods.
Goo
I think I have just about cleaned up the controllers code so that it is now
transparent. As a result of this clean-up I have managed to replace all
those boost::signals in frontends/Dialogs.h with normal C++ class methods.
Similarly, I am about to replace the
boost::signal0 hideDialog;
t
