Tony Rolfe said, 

> On 9 Apr 1999 9:13:42 +0100 Neil Bothwick said:
>> It's a commodity. The standard behaviour of a commodity when clicking
>> the close gadget is to close the window and hide the commodity. The
>> requester is a way of allowing you to use the close gadget to quit
>> without breaking the rules for commodities.

> Sorry, Neil.   I disagree here.

> Most commodities use "Hide" to hide the GUI and "Quit" to quit the
> application.

But we're not talking about a Hide or Quit option, we're talking about
a window close gadget. Try it with Commodities Exchange, the definitive
commodity, the window close button does just that. commodities are
intended to be run in the background, so the window close button only
closing the window is the logical behaviour.

> If I hit any button which gives me an "Are you sure?"
> option and I say "No", I expect the application to leave everything as
> it was.    If the button says "Quit" and I change my mind, I don't
> want the application making some arbitrary decision as to what I
> really meant.

The button doesn't say "Quit". It's a close gadget. The requester is
effectivly asking you "do you want to quit the program as well as
closing the window". The only "bug" here is the wording of the
requester could be a lot clearer.

> My suggestion would be to add a "Hide" button and make them both
> behave intuitively.

The window close gadget *is* the hide button for a commodity. The
confusion arises because all MUI applications are implemented as
commodities, even though many of them aren't fulfilling the intended
role of a commodity. I would say the NC dock shouldn't be a
commodity, whereas Genesis should. But MUI give the programmer no
choice in this matter.


Neil
-- 
Neil Bothwick - http://www.wirenet.co.uk   icq://16361788
Connected via Wirenet,The UK's first Amiga-only internet access provider
--
Top Oxymorons Number 3: Working vacation

Reply via email to