Surely there are standard user interface conventions available for
deciding on what should be done in such cases.
Window closing etc. has been around for getting onto two decades.
Something doesn't sound right when developers have to have long
discussions on it.
Aren't these types of rules built into many of visual development
systems???
Might be an idea to survey many applications that have been around
and accepted for some time, make a list of THEIR
user interface details with pros and cons then decide from there
rather than trying to reinvent the proverbial wheel yet again.
I have long been of the opinion that consistency and convention
should be bywords in user interface design.
José> seems to have the idea about looking for conventional methods:
"It closes the tab, actually." Is this conventional? OK if it is.
Or just another example of "convention" being overlooked and the poor
user of different programs having to be continually confused by
different responses from different programs.
"José" == José Matos <[EMAIL PROTECTED]> writes:
José> Firefox works like that, File->Close closes the current window
José> and if there are no more windows it quits.
It closes the tab, actually.
"It closes the tab, actually." Is this conventional? OK if it is.
Or just another example of "convention" being overlooked and the poor
user of different programs having to be continually confused by
different responses from different programs.
Sorry, but I grew up in a software development world where these
things were considered extremely important.
Hoping these comments might be helpful, though, I admit, not very
constructive,
Roger
