[REQ] Command Browser, usercmd.ini, parameter display

[icfu]

It's not really useful to have dozens of identical "descriptions" in there, like "cmd.exe /c".

Parameters should be visible as well, either in a new column or visually separated with a TAB or so.

Icfu

[solid]

Support.

[HolgerK]

It's not really useful to have dozens of identical "descriptions" in there, like "cmd.exe /c".

A tooltip text as description can prevent this.

Parameters should be visible as well, either in a new column or visually separated with a TAB or so

Support++

Regards,
Holger

[StatusQuo]

Support.

A tooltip would not help much IMO,
because checking a list of "cmd.exe /c" entries would be very slow this way.

A separate column could be more useful,
although it would shorten the space for the "command" content.

Another solution could be to just display command and parameters together there -
the information is just used to see what the command does, so strictly separating the command from parameters is maybe not that important there.
This is what I would prefer.

[HolgerK]

A tooltip would not help much IMO,
because checking a list of "cmd.exe /c" entries would be very slow this way.

May be a misunderstanding?
What I meant was:
If one defines the tooltiptext, this text is actual shown instead of the command text!

Anyway, I support the proposal to include the parameter text to the description (if no tooltiptext is defined).
It isn't very comfortable yet, to copy command and parameter text into the tooltip text field.

Regards,
Holger

[StatusQuo]

May be a misunderstanding?
What I meant was:
If one defines the tooltiptext, this text is actual shown instead of the command text!

Yes, indeed a misunderstanding.
I thought of popping up tooltips when hovering a line with the mouse
(therefore I never thought of filling in something there).

Thanks for the hint, that's at least a nice (undocumented?) workaround.

Anyway, I support the proposal to include the parameter text to the description (if no tooltiptext is defined).