| Summary: | Workspace name not updated after typing existing config name | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Dani Megert <daniel_megert> | ||||
| Component: | UI | Assignee: | Markus Keller <markus.kell.r> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | darin.eclipse, remy.suen | ||||
| Version: | 3.7 | Flags: | darin.eclipse:
review+
|
||||
| Target Milestone: | 3.7 M3 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Dani Megert
Created attachment 181852 [details]
Fix
Darin, I think we should fix this for M3. 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... > 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. Applied/Fixed. Verified in I20101028-1800. |