>>>>> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> My plan is to change this accessor to:
Abdelrazak> ErrorList const & ControlErrorList::errorList(string const
Abdelrazak> & type) const {
Abdelrazak> return kernel().bufferview()->buffer()->errorList(type);
Abdelrazak> }
This would definitely break my approach. The problem is that the
dialog code provides too places to handle changes
- build_dialog(): this is called at show, but only if the dialog
does not exist. Not good for our needs.
- update_contents(): this is what we use. The problem is that is
called everytime the dialog gets an update event. This is why I use
my magic flag to tell whether update is really needed.
Abdelrazak> I am not sure in practice how this is going to be
Abdelrazak> implemented in the frontend but I guess we will need some
Abdelrazak> new menu entries.
I'd rather see a unique entry, and a dialog that allows to switch
between the different available error lists.
JMarc
