Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 325020 - XGCONF should warn user before removing a module from current configuration
Summary: XGCONF should warn user before removing a module from current configuration
Status: ASSIGNED
Alias: None
Product: RTSC
Classification: Technology
Component: Tools (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Jon Rowlands CLA
QA Contact:
URL:
Whiteboard: target: 3.40
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-10 19:38 EDT by David Friedland CLA
Modified: 2014-02-26 00:27 EST (History)
1 user (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 David Friedland CLA 2010-09-10 19:38:54 EDT 
Build Identifier: RTSC/XDCTools 3.20.01.42-eng

If a user invokes a "stop using" module command, it will blow away the module and any instances created under the module without any warning or request to the user for confirmation.

Reproducible: Always

Steps to Reproduce:
1. Drag a new SYS/BIOS module from the available packages screen to the Outline screen (e.g., Task).
2. Create one or more new instances under that newly enabled module (e.g., Task1, Task2, etc.) by right-clicking on the module and selecting "New..."
3. Disable the module by right-clicking on the module name and selecting "Stop Using..."
4. BAM, the module and created instances are blown away.  No way to undo the deed.  No warning to the user that this would happen.  No request for confirmation that this is what the user really wants to do.