Bug 311987 - [Wizards] [Progress] Cancel button in wizard progress dialog should allow me to cancel out of entire operation
Summary: [Wizards] [Progress] Cancel button in wizard progress dialog should allow me ...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-06 18:39 EDT by John Cortell CLA
Modified: 2019-09-06 16:15 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Cortell CLA 2010-05-06 18:39:53 EDT 
I opened bug # 311917 because I thought the update manager wouldn't let me cancel a long running operation. Turns out I didn't notice the new little cancel box. Fair enough. User error. But the user who just wants to cancel out of the entire Install New Software operation shouldn't have to hit two cancel buttons. Intuitively, he will reach for the Cancel button in the dialog because he wants to cancel out of everything related to that dialog. I believe that button should be enabled and hitting it should cancel out of everything related to the update manager. If he wants to cancel out of just the reqs and dependencies gathering, he has that option via the little red box.
Comment 1 Susan McCourt CLA 2010-05-06 20:22:03 EDT 
This is referring to the stop button introduced in wizards in bug 287887.

The request here is that you shouldn't have to cancel twice.
Note that prior to the stop button, you still had to cancel twice.

So I think we can interpret this bug to mean...provide both a way to cancel the long running operation in a wizard, and a way to cancel the entire wizard.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:15:33 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.