Kalle,
you can imagine two types of "input" in the dialog:
1) "input" that changes the state of the relevant Params struct and which
can, therefore, be "applied";
2) "input" that does not change any params, but which is used to navigate
around the dialog. Eg, clicking on the browsers in the cit
Hi,
I am a bit confused about the calls to ButtonController::input() which are
done at the end of the XForms input() methods. My guess was that this is used
to enable/disable the OK, Apply etc. buttons. However, when I call this, I
get into an endless recursion in the input() methods.
Followi
On Mon, 15 Jan 2001, Angus Leeming wrote:
> Hello, Allan.
Hi Angus!
> Let me start with a justification of all this: I'd like to ease the pain of
> porting the dialogs to other GUIs by ensuring that they have only a minimum
> of things to do. We have occasional complaints from John and Marco ab
Hello, Allan.
Let me start with a justification of all this: I'd like to ease the pain of
porting the dialogs to other GUIs by ensuring that they have only a minimum
of things to do. We have occasional complaints from John and Marco about
breaking their ports. Matthias Ettrich was rather more
On Fri, 12 Jan 2001, Angus Leeming wrote:
> Allan,
>
> I've worked out how to put an abstract ButtonControllerBase in the
> ControlCitation class, or rather in a class that ControlCitation can be
> derived from.
Are you sure you want an inheritance relationship?
I'm not sure what sort of separa
Allan,
I've worked out how to put an abstract ButtonControllerBase in the
ControlCitation class, or rather in a class that ControlCitation can be
derived from.
I have one question regarding your ButtonController class. In the header file
there is:
// Somebody else owns the FL_OBJECTs
