On Tue, 3 Apr 2001, Angus Leeming wrote:
> I think that this is exactly what Kalle was talking about this morning, no?
>
> Why not just not pass this operation though the (button) controller at all.
> Ie, this is a "manipulation" rather than an "input". The Apply/Ok buttons
> will not change state, so cheat because the ButtonController isn't really
> sophisticated enough to deal with this case cleanly.
actually, you're probably right for this case, since they can't be activated in
a read-only situation. Good point. Although I would humbly suggest special casing
things like this is a bit ugly. And what happens if we have a button that can be
used in read-only state, and can modify the dialog contents (but obviously not the
STATE of the contents) ? I can't think of a case yet, but ...
I'm prolly missing something here ...
john
--
"Creating laws which cannot be universally enforced leads to arbitrary enforcement."
- Upsilon, /.
