Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kill conformation dialog in GCS is not optional #873

Closed
OpenUAS opened this issue Oct 23, 2014 · 8 comments
Closed

Kill conformation dialog in GCS is not optional #873

OpenUAS opened this issue Oct 23, 2014 · 8 comments
Labels
Enhancement Improve upon exiting functionality GCS
Milestone

Comments

@OpenUAS
Copy link
Contributor

OpenUAS commented Oct 23, 2014

As a user I like to be able to instantly "kill" a UA and at the moment a dialog to confirm pops up.

The reason for a lot of users is obvious. For more advanced users and fast mishaps scenarios not so good.

An additional parameter to be able to disable the conformation at startup would be a satisfactory solution for now.

@OpenUAS OpenUAS added the GCS label Oct 23, 2014
@OpenUAS OpenUAS added this to the v5.6 milestone Oct 23, 2014
@OpenUAS OpenUAS added the Enhancement Improve upon exiting functionality label Oct 23, 2014
@alonsoac
Copy link
Contributor

What about removing the confirmation but requiring 2 clicks so that an
accidental click does not cause a problem? Considering that there is no
retry of the command and no guarantee that it will be received one would
really need to click it multiple times until the kill is confirmed somehow.

On Thu, Oct 23, 2014 at 1:39 PM, OpenUAS notifications@github.com wrote:

As a user I like to be able to instantly "kill" a UA and at the moment a
dialog to confirm pops up.

The reason for a lot of users is obvious. For more advanced users and fast
mishaps scenarios not so good.

An additional parameter to be able to disable the conformation at startup
would be a satisfactory solution for now.


Reply to this email directly or view it on GitHub
#873.

@kevindehecker
Copy link
Contributor

From a GUI design point of view, implementing a double click should only be done when it is clear to the user that a double click is required. A button does not normally require double click, so a user would be annoyed if he would find out at all.

I think the opt out parameter is better, preferably with an added checkbox ("[x] do not show this message again", in the conformation dialog)

@flixr
Copy link
Member

flixr commented Nov 19, 2014

Just for clarification: you don't need a double-click, but rather two clicks, once for kill and once to confirm in the popup...

@kevindehecker
Copy link
Contributor

I was responding to the double click idea of alonsoac.

@flixr
Copy link
Member

flixr commented Nov 19, 2014

Right, ok...

@alonsoac
Copy link
Contributor

Well I meant two clicks. One to unlock the button and another to confirm
the kill but on the same button not on separate dialog. If no click within
a few seconds then lock button again.
The point is some kind of confirmation but not in annoying separate dialog.
On Nov 19, 2014 4:10 PM, "kevindehecker" notifications@github.com wrote:

I was responding to the double click idea of alonsoac.


Reply to this email directly or view it on GitHub
#873 (comment).

@kevindehecker
Copy link
Contributor

Ah, like on of them self-destruct buttons !

That'd be ingenious.

@flixr flixr modified the milestones: v5.8, v5.6 Jun 24, 2015
@OpenUAS
Copy link
Contributor Author

OpenUAS commented Dec 7, 2015

THX, my shaky cold fingers in the outside testingfields all thank you :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Improve upon exiting functionality GCS
Projects
None yet
Development

No branches or pull requests

4 participants