D
Dave
No GUI should EVER interrupt the user's active use of an
application by bringing another app to the foreground and
making it active.
It's infuriating to be typing like mad in one program,
have another pop to the foreground (for ANY reason) and
find you've inadvertantly pressed keys for a half-dozen
commands in the new app.
It doesn't matter whether the user initiated the event
either (say by loading another app). The user needs to
keep total control of what apps are active at all times--
if the system MUST interrupt, it should only do so by
disabling keyboard inputs so as to avoid the above
problem.
To me this is a fundamental shortcoming of modern GUIs--
Windows included--and it's gone overlooked too long.
/Rant finished.
Dave
application by bringing another app to the foreground and
making it active.
It's infuriating to be typing like mad in one program,
have another pop to the foreground (for ANY reason) and
find you've inadvertantly pressed keys for a half-dozen
commands in the new app.
It doesn't matter whether the user initiated the event
either (say by loading another app). The user needs to
keep total control of what apps are active at all times--
if the system MUST interrupt, it should only do so by
disabling keyboard inputs so as to avoid the above
problem.
To me this is a fundamental shortcoming of modern GUIs--
Windows included--and it's gone overlooked too long.
/Rant finished.
Dave