Bug 102039 - [introduce parameter] cell editor hides proposed name
Summary: [introduce parameter] cell editor hides proposed name
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Markus Keller CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-28 12:10 EDT by David Saff CLA
Modified: 2023-09-24 00:13 EDT (History)
0 users

See Also:

Attachments
Screenshot (11.12 KB, image/png)
2005-06-28 12:11 EDT, David Saff 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 David Saff CLA 2005-06-28 12:10:43 EDT 
In 3.1 final (hurray!)

Code:

public class LongClassName {
  private LongClassName foo() {
    return new LongClassName();
  }
}

Highlight "new LongClassName()", and choose Refactor > Introduce Parameter.  The
window that comes up cuts off the left side of the proposed parameter name.  The
parameter name proposed can be perfectly reasonable, but the user may think it
needs to be edited.  Screenshot will be attached.
Comment 1 David Saff CLA 2005-06-28 12:11:32 EDT 
Created attachment 24092 [details]
Screenshot
Comment 2 Martin Aeschlimann CLA 2005-06-29 11:39:48 EDT 
Markus, is this a JFace issue?
Comment 3 Eclipse Genie CLA 2019-10-13 14:24:38 EDT 
New Gerrit change created: https://git.eclipse.org/r/151018
Comment 4 Eclipse Genie CLA 2021-10-03 00:15:17 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Eclipse Genie CLA 2023-09-24 00:13:53 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.