Skip to content
This repository has been archived by the owner on Apr 4, 2024. It is now read-only.

All GUI screens need a BUSY indicator #14

Open
jcoffland opened this issue Apr 1, 2015 · 0 comments
Open

All GUI screens need a BUSY indicator #14

jcoffland opened this issue Apr 1, 2015 · 0 comments
Assignees

Comments

@jcoffland
Copy link
Member

Reported by @bb30994 on 10 Sep 2010 21:36 UTC
The UPDATING indicator covers a small fraction of the times when the GUI is unable to manage a new request. e.g.- choosing Pause or Finish takds several seconds during which time it's not clear that the mouse-click has been accepted. Selecting some other function during this time often leads to a GUI hang.

When a click is accepted IMMEDIATELY turn on some kind of (red?) BUSY or WAIT indicator and reset it (to a neutral color) once the client has delivered a COMPLETED status to the GUI.

The GUI-CLIENT interface (and AFAICT the Client) is not designed to deal with multiple simultaneous requests. Unlke other GUIs, it's also much slower than other methods of doing things so the user expectations mus be managed -- perhaps by informing him that further input is (temporarily) not acceptable.

@jcoffland jcoffland self-assigned this Apr 1, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant