This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 113744

Summary: Ability to provide custom action for controlling task cancellation
Product: platform Reporter: _ gsporar <gsporar>
Component: ProgressAssignee: Jan Peska <JPESKA>
Status: NEW ---    
Severity: blocker CC: mkrauskopf
Priority: P3 Keywords: API, UI
Version: 6.x   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Exception Reporter:

Description _ gsporar 2007-08-24 15:44:34 UTC
When I click the small 'x' next to the small status control for WEBrick, the IDE displays a dialog that says:

Are you sure you want to cancel WEBrick for <project name> on 3000?

This seems confusing to me because "cancel" is a bit vague and is normally used in warnings to give the user the option
to *not* do what they just selected (e.g. "Click cancel to continue or yes if you really want to exit").  What the IDE
is actually going to do is shut down WEBrick, right?  So it seems the message should be:

Are you sure you want to shut down WEBrick for <project name> on 3000?
Comment 1 Torbjorn Norbye 2007-08-24 17:39:39 UTC
This message is provided by the progress support and is the same for -all- tasks that you attempt to canc^H^H^H^H stop.
Perhaps the message should be "Are you sure you want to terminate {x}", or perhaps "stop" instead of "terminate" ?
Comment 2 Milos Kleint 2007-09-24 09:42:55 UTC
*** Issue 110459 has been marked as a duplicate of this issue. ***
Comment 3 Milos Kleint 2007-09-24 09:43:36 UTC
*** Issue 110459 has been marked as a duplicate of this issue. ***
Comment 4 Martin Krauskopf 2007-09-24 10:28:33 UTC
We agreed with Milos that this and issue 110495 will be solved with this enhancement. So changing subject accordingly.
Comment 5 Martin Krauskopf 2007-09-24 10:30:04 UTC
*** Issue 110459 has been marked as a duplicate of this issue. ***
Comment 6 Torbjorn Norbye 2007-09-24 21:41:40 UTC
I posted the following to a duplicate of this (110459), reposting here to make sure it's addressed:
I'm not sure adding an API for custom termination interaction is the best way to do it. 

Whether or not a user program should be killable without interaction is not an attribute of the technology, it's an
attribute of the developer type.

Put another way, there are Java developers who want to be able to terminate their running program / test without
interaction, just as there are Ruby developers who may want the confirmation dialog.

Putting this logic into specific task handlers will just encourage different behavior in places where the difference
doesn't make sense.  Instead, whoever is posting the "Are you sure?" dialog today needs to add a checkbox to suppress
show-in-future, and persist the state.