How about Ctrl+Shift+Alt+Space completes the code with empty values.

Like this:

Trim();

After Ctrl+Shift+Alt+Space inside that parentheses makes this:

Trim('');

Just, another idea. :)

Or the CTRL+SHIFT+C continue to complete code, on this cases as well :)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120214/6c5c9bda/attachment.html>

Sure will be better than memorize another shortcut is to specialize one thats already exists.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120214/576a413a/attachment.html>

Why not simply type the single quote key twice, instead of a complex four-key combination. Thus, resulting in less keys to type. I can suggest a good typing tutor program too, if you have problems typing. ;-)

Just another idea. :)

You do know shift-ctrl-space ?
Which opens a hint showing the possible parameter list(s). That also has the advantage to work if there are overloaded versions.

In 0.9.31 you can then insert the one you need, with the mouse (sorry no keyboard)

Trim is bad example :) but if you wanted Ctrl+Shift+Alt+Space to expand, e.g.

AnsiReplaceString()
into
AnsiReplaceString('','','')

What would you put as 'empty' parameter for functions that have numeric meaning, and don't really tolerate 0 as input
(hypothetical: function Divide(A: integer; B: integer):Real; if you expand Divide() to Divide(0,0) and forget to put some meaningful constant into B (or variable) you'll end up with executing div/0 and as such, an error)

As such such expansion IMO is futile.

L.

I know. Thanks.

As a code complementation suggestion theres no need to put 0 instead is better only put the comma when the parameter is required.

This idea came when i had to type about ten times a function like this func('', '', [], '', [] , []); wich time the parameters changed, of course i did ctrl+c ctrl+v. This would be only a very subtle behavior. Like every one knows, details are in the art of the elegancy.

[...]

Well as such, it /may/ be viable and useful (put just commas _between_ parameters) but '' and [] is making an exception to the rule so I'd rather func(,,,,,) or func( , , , , , ) than what you suggest; This however requires that you can only add parameters to the last place of definition, and never-ever reorder them, having the editor track that you've added a parameter in the middle of the definition and change invocation accordingly is probably not going to be well-accepted maintenance-wise...

What for the functions that have parameters with default values, that are only used in exceptional cases ? Do you want to show the non-default param placeholders only?

L.

The exceptions are the ones that makes shine.

func(,,,,,) or func( , , , , , ) than what you suggest; This however requires that you can only add parameters to the last place of definition,

Why is that so? Is only a code complementation.

and never-ever reorder them, having the editor track that you've added a parameter

Same here.

The default lets not complete, after all, they have default values just because isn`t need in a considered number of cases.

Ctrl+Shift+C specialized is the better option for, i guess.

And of course there`s the overload statements, that can receive an special/exceptional treatment as well.