Bug 125378 - [typing] Comma should advance to next completion argument
Summary: [typing] Comma should advance to next completion argument
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-26 15:03 EST by Nick Edgar CLA
Modified: 2006-01-27 02:44 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Edgar CLA 2006-01-26 15:03:59 EST
build I20060119

Type a statement like:
  images.put(imageDesc, image);
where images is a Map.

As you type "put(", code completion happens and it completes to:
  images.put(arg0, arg1)
with arg0 active.

Type "imageDesc" then ",".
After the comma, the tooltip advances to arg1, but the text does not.  It's now showing:
  images.put(imageDesc,|, arg1)  (where | is the caret)

Continue typing " image);" as if you hadn't been aware of the code completion.
The ) and ; do their smart thing.
The end result is:
  images.put(imageDesc, image, arg1);

I would expect the content assist to not interfere with normal typing.
The typed comma should match the generated comma and simply advance to the next argument, with subsequent typing replacing the next argument, as if I had pressed Tab instead of comma.
Comment 1 Tom Hofmann CLA 2006-01-27 02:44:53 EST
Valid request - this fits well with the goal that any extra characters inserted behind the caret should not interfere with your normal typing.

This is not something we can accomplish with today's typing infrastructure. Linked mode only supports "exit characters" that leave the linked mode and jump somewhere else. To implement this request, we need a "shadow text" feature similar to what open office and others do.