Some other (useful?) wishlist options.

[r0n]

Sorry for this long list.
Numbers 1 to 13 could be considered as 'primary' wishlist / 'handy'
Numbers 14 to 20 could be considered as future/luxury.

1. Vertical dot tab indicators (tab/indentation guides): http://www.scintilla.org/styledmargin.png
   
2. Right click on macro/function/... and then select 'copy path'
   
3. When creating a dialog the user could also specify an extra item: 'variable name' for the object (listbox, edtitfield, etc...).
   This would add an extra item in each line of the green commented dialog deceleration code. The user could create code that in 1 click generates all the variable decelerations for each dialog object.
   
4. Be able to create "local" functions in a macro itself. The created function would then only be accessible for the macro itself.
   The functions could be declared first and then the normal code below. This could reduce external functions and yet keep code for a macro more manageable?
   
5. Extra 'end option:''end -1' does not process code below. I looked in the help-file for that option, but couldn't find something like that.
   'end' with the option NOT to process code below the 'end' command , so it would treat the code below the 'end' command as 'none existing'.
   (flag = -1). As I stated earlier I looked for this in the help about the 'end' command, but couldn't find the desired function (it has flags 0-3, 4 8 16 32)
   
6. Transfer containers (variables), for example you have array "arr" and string "_s", normally you could "arr=_s" which in one line creates an array "arr" from the contents of string "_s".
   The 'transfer' method could be used to transfer the contents of container "_s" to container "arr".
   With transferring I mean 'move' each item (line) from "_s" to array "arr". It is a more memory friendly way (in stead of copying).
   
7. Listbox (list) has the cancel button reserved for '0' , is it possible to have it mapped to '-1'.
   This would make the filling of the listbox from a zero-index-based array a bit easier.
   
8. A (free) totally stripped down version of QM with primary function of running imported .qml macros.
   No editing of macro's possible, so only the tree and output window would be shown with basic settings menu: backup, options, ....
   Could this remove some limitations of .exe (RunTextAsFunction,....etc) at the same time keep the totally stripped down version free?
   The code edit pane would only show Rich Text + images (if possible) So the macro developer could show instruction in the Code editor pane.
   
9. Export 'ALL' item: option to export ALL in one file (a sort of second backup)
   Maybe it would be a good idea to have an explicit function for backing up at users will.
   At the moment there is: 'auto backup' and the 'save'-icon. Something like 'file' >> 'Export ALL'
   
10. Optional questionmark button [?] in the default Dialogs: Message Box, Input Box, Password Input Box, Listbox.
    This button could be mapped (programmed) to a usermade function/macro. This could help to make a quick help-reference buttons for .exe macros which use the default pre-made: Message Box, Input Box, Password Input Box, Listbox.
    
11. read-only for macros/functions/... (avoid accidental change, now only folder can be set as 'read only')
    And a special 'change' check-box next the 'read-only' check-box in macro/function/.. properties.
    This would make the macro/function/ ... editable, BUT on loose focus (go to other folder/macro/function/...) it reverts back to original code.
    This is good for quick testing other parameters and such.
    
12. clipboard monitor also default incorporated in next version. To clarify "clipboard_copy_trigger": Clipboard copy triggers
    
13. Unused variables check. Like the 'search' function but now it only highlights a declared variable that is not used in a script.
    
14. When a macro name is changed a dialogbox pops up and asks if the name should also be changed in the code of other macros.
    
15. When creating a small dialogbox some options on the left side are not viewable (click-able), styles, events, delete....
    Maybe the design window could be made resizable and then on top of that the canvas could be rendered which is also resizable but could be left 'small'.
    Because the window below the canvas (design window) is big enough to show all items the user could set the canvas as big or small as the user wants.
    This could make all buttons viewable while the canvas size could be small.
    
16. Auto-completion when programming for declared variables. For example the following is declared: "ARRAY(str) test_arr" , when the first letter of "test_arr" is typed in the beginning of a new line QM could display an auto completion selection list just like when pressing the '.'
    
17. QM safety feature (which could be toggled on and of): limit threads or limit output to 1000 (avoid loop, extreme output). Or with the added safety feature of running longer then 30 seconds would automatically end the macro.
    This would be for beginners or when testing macros for which you know you a have short execution time.
    
18. ICsv output row: for example you have ICsv 'test' then: "out test.Row(1)" outputs the full row, and for example "str x=test.Row(1)" Row 1 would be put in container "x"
    
19. Optional include code in exe, the code could be encrypted using the users registration code for QM could be used for decryption?
    The registration code wouldn't saved in the .exe. To clarify: The user could go in the menu select 'file >> extract code' and then users registration code (or part of the registration code)
    would be used to decrypt the code and then import the code in a separate folder named to .exe name.
    
20. Undo 'clear output-field' (just one undo is enough?).

[Gintaras]

Thank you. Let me comment some.

1. ?
2. I often need to copy name. Path also useful. Probably will add 'Copy name Ctrl+C' and 'Copy path Ctrl+Shift+C'.
3. Now the first 3 characters of control text are added to the variable name.
Tip: In macro you can declare reference variables like str& k=cb1002Sel and then use k instead of cb1002Sel.
4. This should be in 2.4.2 or 3.
5. Isn't it #ret ?
6. Now can use ARRAY(lpstr) and tok with flag 1:
str s="one[]two[]three"; ARRAY(lpstr) a; tok s a -1 "[]" 1
s still contains the strings, but newlines are replaced to null characters. a elements point to strings in s.
9. You can copy file. Maybe will add functions _qmfile.Backup and _qmfile.GetLoadedFiles.
14, 13, 10. Probably will add something like this.

[r0n]

Ok thank you!

With the first one I think I didn't explain right. What I meant was a vertical dotted line like in the screenshot:
http://www.scintilla.org/styledmargin.png
So it is easier to count the amount of tabs. Maybe this is a better example:
http://www.joeflash.ca/blog/images/FB_f ... des_sm.jpg
Indentation guides are vertical lines in the editor that follow the tab stops in the document so that code blocks can be visually tracked.