Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319801 - A warning on the refactor dialog will disable next/finish buttons
Summary: A warning on the refactor dialog will disable next/finish buttons
Status: CLOSED DUPLICATE of bug 311696
Alias: None
Product: Tigerstripe
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-13 19:31 EDT by Navid Mehregani CLA
Modified: 2010-08-25 16:47 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Navid Mehregani CLA 2010-07-13 19:31:31 EDT
Build Identifier: 

When initially creating a Datatype artifact, user can give it a name that starts with a lowercase letter.  However, when user tries to later rename the artifact to a different name that starts with a lowercase letter, the next/finish buttons on the refactor dialog are disabled.

Reproducible: Always

Steps to Reproduce:
1. Right click on your TS project > New > Datatype
2. Call it 'my_datatype' and click on finish.  Notice the warning that's displayed in the dialog
3. Right click on the newly created datatype > Refactor Model > Rename > call it 'my_datatype2'.  Notice the warning is displayed again.  However, the next/finish buttons are disabled.  You have to give it a name that starts with an uppercase letter in order for the buttons to get enabled.  

This behavior is inconsistent, since the user is allowed to initially create this artifact with lowercase letters.  Note that the same behavior is observed with other artifacts such as Enumeration.
Comment 1 Richard Craddock CLA 2010-07-14 04:11:46 EDT
See also 311695
Comment 2 Daniel Johnson CLA 2010-08-25 16:39:05 EDT
This is a duplicate of 311696
Comment 3 Navid Mehregani CLA 2010-08-25 16:47:39 EDT
(In reply to comment #2)
> This is a duplicate of 311696

Yes, it is.  Thanks!

*** This bug has been marked as a duplicate of bug 311696 ***