On Thu, 5 Apr 2001, John Levon wrote:
> On Thu, 5 Apr 2001, Allan Rae wrote:
>
> > That's what the input checking routine is for.
> >
> > The fact that an input has changed isn't significant. The problem is
> > whether or not that change has resulted in a valid contents of the dialog
> > or not. If the contents are valid then Okay and Apply should be
> > enable-able (if the state machine is in an appropriate state).
>
> The problem for me is that this also enables anything you added with
> addReadOnly, if the dialog is read-write. Ideally these two things
> should be split somehow, I'm sure you two controller bods can come up
> with something clever that works ;)
I don't understand why this is a problem. If we have a read-write
document then all the read-only list widgets should be enabled. What
operation are you expecting?
Do you want some widgets that are only enabled when we have a read-only
document?
Hmmm... okay maybe this is the shared management problem again. If I can
get this RBG [RadioButtonGroup] patch working we should be able to define
a RBG then toggle different radio buttons to get different sets of widgets
activated/deactivated.
Then I can generalize the patch to only use a set of ints rather than a
whole RBG (hhmmmm maybe I should do this now it might make it easier to
get working). That'd allow you to define within your dialog an enum to
define the sets of widgets that can be activated together and inform the
BC when the enum state changes. bc().refresh() then activates the
appropriate widgets -- the dialog just has to track which set should be
active. Hmmm yeah I think that'd probably be easier to implement than the
RBG specific thing I put on ice months ago.
Allan. (ARRae)
