Home » Newcomers » Newcomers » 3.1.1: Auto-complete of inner class completes FQCN, with "$" separators
3.1.1: Auto-complete of inner class completes FQCN, with "$" separators [message #118589] |
Sun, 20 November 2005 04:36 |
David M. Karr Messages: 143 Registered: July 2009 |
Senior Member |
|
|
If I start typing the name of an inner class and press Ctrl-space for
auto-completion, it does a couple of undesirable things.
First, for the top-level class, even if I've already imported the class,
it adds in the FQCN, instead of the simple class name.
Second, for each of the inner classes, except for the last one (the one
I was trying to auto-complete), it uses "$" for the class name
separators instead of ".".
After doing the completion, I have to edit the line, removing the
package path of the top-level class, and changing the "$" to ".". I
believe the latter step isn't strictly necessary, it's just cleaner to
use periods than "$".
|
|
|
Re: 3.1.1: Auto-complete of inner class completes FQCN, with "$" separators [message #118739 is a reply to message #118589] |
Mon, 21 November 2005 19:20 |
Eclipse User |
|
|
|
Originally posted by: eclipse3.rizzoweb.com
David Karr wrote:
> If I start typing the name of an inner class and press Ctrl-space for
> auto-completion, it does a couple of undesirable things.
>
> First, for the top-level class, even if I've already imported the class,
> it adds in the FQCN, instead of the simple class name.
>
> Second, for each of the inner classes, except for the last one (the one
> I was trying to auto-complete), it uses "$" for the class name
> separators instead of ".".
>
> After doing the completion, I have to edit the line, removing the
> package path of the top-level class, and changing the "$" to ".". I
> believe the latter step isn't strictly necessary, it's just cleaner to
> use periods than "$".
Do you have a concrete example that demonstrates this?
I've use auto-complete with inner classes many times and don't recall
ever seeing such behavior.
Also, which version of Eclipse and what JVM?
|
|
|
Re: 3.1.1: Auto-complete of inner class completes FQCN, with "$" separators [message #118817 is a reply to message #118739] |
Mon, 21 November 2005 21:12 |
David M. Karr Messages: 143 Registered: July 2009 |
Senior Member |
|
|
Eric Rizzo wrote:
> David Karr wrote:
>> If I start typing the name of an inner class and press Ctrl-space for
>> auto-completion, it does a couple of undesirable things.
>>
>> First, for the top-level class, even if I've already imported the class,
>> it adds in the FQCN, instead of the simple class name.
>>
>> Second, for each of the inner classes, except for the last one (the one
>> I was trying to auto-complete), it uses "$" for the class name
>> separators instead of ".".
>>
>> After doing the completion, I have to edit the line, removing the
>> package path of the top-level class, and changing the "$" to ".". I
>> believe the latter step isn't strictly necessary, it's just cleaner to
>> use periods than "$".
> Do you have a concrete example that demonstrates this?
> I've use auto-complete with inner classes many times and don't recall
> ever seeing such behavior.
> Also, which version of Eclipse and what JVM?
Providing the complete example might be a little complicated, but I used
XMLBeans 2.1.0 with Eclipse 3.1.1 and JDK 1.4.2. I generated a class
hierarchy from an xsd and then I tried to reference the generated classes
in my code, which is where I saw this behavior.
|
|
|
Re: 3.1.1: Auto-complete of inner class completes FQCN, with "$" separators [message #119024 is a reply to message #118817] |
Tue, 22 November 2005 18:31 |
Eclipse User |
|
|
|
Originally posted by: eclipse3.rizzoweb.com
David Karr wrote:
>> Do you have a concrete example that demonstrates this?
>> I've use auto-complete with inner classes many times and don't recall
>> ever seeing such behavior.
>> Also, which version of Eclipse and what JVM?
>
>
> Providing the complete example might be a little complicated, but I used
> XMLBeans 2.1.0 with Eclipse 3.1.1 and JDK 1.4.2. I generated a class
> hierarchy from an xsd and then I tried to reference the generated
> classes in my code, which is where I saw this behavior.
Well, I urge you to take a few minutes to build a self-contained test
scenario. Without that you can't realistically expect others to be able
to reproduce it, and if we can't reproduce we can't explain or debug.
Eric
|
|
| |
Goto Forum:
Current Time: Sat Nov 09 00:05:59 GMT 2024
Powered by FUDForum. Page generated in 0.08031 seconds
|