Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358081 - Error message is not correct in Name field
Summary: Error message is not correct in Name field
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Paul Harmon CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-19 05:52 EDT by Thomas Wu CLA
Modified: 2017-02-23 14:20 EST (History)
4 users (show)

See Also:

Attachments
screenshot (18.29 KB, image/png)
2011-09-19 05:54 EDT, Thomas Wu CLA 		no flags Details
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 Thomas Wu CLA 2011-09-19 05:52:32 EDT 
Build Identifier: 20110917

Error message displayed in New EGL Handler wizard is not correct when a user
input some invalid handler name.
Note: There is the same issue in lots of other new part wizard, such as interface, program, etc.

Reproducible: Always

Steps to Reproduce:
Steps to Reproduce:
1. New an EGL projet.
2. Right click the newly created project, then click new handler.
3. In the New EGL handler wizard, input "8" in Name field. 

Actual results: The error message shows "Found gl in 8.egl",
which does not make sense for user.
Comment 1 Thomas Wu CLA 2011-09-19 05:54:18 EDT 
Created attachment 203577 [details]
screenshot
Comment 2 Xiao Bin Chen CLA 2011-10-25 01:35:48 EDT 
Hi Paul,

Wizard for creating EGL file will use EGLNameValidator to validate if this file name is correct or not. And also if there is error with a file name, the error message will be provided by EGLNameValidator which located in org.eclipse.edt.compiler/internal/core/validation/name/EGLNameValidator. So I change the owner to you.

By the way, this defect also exist in RBD.
Comment 3 Matt Heitz CLA 2012-11-15 13:47:46 EST 
Fixed with commit 5ef582a5aaa66ee0918688d0f6bb478eeb1cedde.