Bug 165430 - code snippets: ask for values once
Summary: code snippets: ask for values once
Status: RESOLVED FIXED
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: snippet (show other bugs)
Version: git master
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-30 17:11 UTC by Maciej Pilichowski
Modified: 2009-03-24 13:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2008-06-30 17:11:10 UTC
Version:            (using KDE 3.5.9)

code snippets: ask for values once

Define snippet with 3 variables and you will have to gone through 3 dialogs!

Please:
a) merge all those in one dialog
b) use edit-boxes -- if this is not useful for somebody provide separate delimeter for one-liners, at least I am not ready to write a story as a variable

and sub-wishes:
c) drop "make it default" (you can't use it anymore -- put it in definition, one checkbox less every time, the better!)
d) show the name of the variable, not decorations --> x, instead of $x$, it only makes reading harder
Comment 1 Andreas Pakulat 2008-06-30 17:50:01 UTC
Definetly, I'd actually consider this a usability bug. I think it would be nicer to do this without any dialogs at all and directly jump inside the editor from variable to variable. But I'm not sure this is doable with current KTextEditor interfaces.
Comment 2 Robert Gruber 2009-03-24 10:05:04 UTC
In KDevelop3 you can always define the way how you are asked for a variable's value in the options. Either single query for each variable or one dialog with all variables.

In KDevelop4 the whole thing changed. You will always get a small dialog with an editable table containing all variables of the selected snippet. In that table you can then enter the values for those variables.



Besides that I not sure if I understand what you want to say wich b) and c) ?

For b): Do you mean using a single-line edit field instead of the new used multiline-edit? Anyways, KDevelop4 uses a table to let you enter the variable values. So it shouldn't be any problem there.

For c): Why can't you use it? I use it every day at work. 
If you don't want default values to be save, just leave the checkboxes as they are. You don't have to click them if you don't want the value to be saved. 

For d) You're right, that was changed in KDevelop4.
Comment 3 Maciej Pilichowski 2009-03-24 13:17:05 UTC
ad.b) I meant that I should be able to enter "5,3" as values for x and y (comma is separator here)

ad.c) the more widgets you have the more keystrokes you have to make. Since you wrote "click" I assume you use mouse, but the design UI should be not mouse- or keyboard-centric. Besides, how do you use it (to achieve what goal)?

Changing status to fixed, because it was implemented in the way I wished for.