Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 328742 - Workspace name not updated after typing existing config name
Summary: Workspace name not updated after typing existing config name
Status: VERIFIED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.7 M3   Edit
Assignee: Markus Keller CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-26 12:50 EDT by Dani Megert CLA
Modified: 2010-10-28 02:33 EDT (History)
2 users (show)

See Also:
darin.eclipse: review+

Attachments
Fix (4.66 KB, patch)
2010-10-27 12:44 EDT, Markus Keller CLA 		no flags Details | Diff
View All 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 Dani Megert CLA 2010-10-26 12:50:18 EDT 
I20101025-1800.

The workspace name of a new config is not updated after typing an existing config name.

1. create a new config and close the dialog
2. create a new config ==> New Configuration (1)
3. delete the " (1)" ==> error shown
4. now type a different name
==> workspace location not updated
Comment 1 Markus Keller CLA 2010-10-27 12:44:07 EDT 
Created attachment 181852 [details]
Fix
Comment 2 Markus Keller CLA 2010-10-27 12:45:06 EDT 
Darin, I think we should fix this for M3.
Comment 3 Darin Wright CLA 2010-10-27 12:53:20 EDT 
This appears to be working for me already (using I20101026-2000). Perhaps I don't understand the steps, but when I create a new config the second time and delete the " (1)", and then type new characters, the workspace location is updated...
Comment 4 Markus Keller CLA 2010-10-27 13:00:44 EDT 
> This appears to be working for me already (using I20101026-2000).

Yeah, this only happens after the workspace location has been changed to a location that already exists on the file system. So Dani's steps need a step
"1.5 launch the new config" to show the effects.

Curtis found another scenario where the same problem shows up in
bug 127719 comment 46: When you remove the whole launch config name and the base location already exists, then the updating also stops.
Comment 5 Darin Wright CLA 2010-10-27 13:47:18 EDT 
Applied/Fixed.
Comment 6 Dani Megert CLA 2010-10-28 02:33:23 EDT 
Verified in I20101028-1800.