#2540 closed Feature Request (Completed)
_ArrayDisplay - new parameter - copy rows and column name
| Reported by: | mlipok | Owned by: | J-Paul Mesnage |
|---|---|---|---|
| Milestone: | 3.3.9.23 | Component: | Standard UDFs |
| Version: | Severity: | None | |
| Keywords: | Cc: |
Description
Please consider adding a new parameter to the function.
Description of action parameter:
Use of the cause is that after pressing the "Copy Selected" to the clipboard in addition to the contents of the table getting the names of columns and rows numbering
Alternatively, instead of adding a parameter, please consider adding a new secondary key.
ie in addition to the standard "Copy Selected" new "Copy Selected (row count and column name)" is of course a similar effect to that described above.
I even think that the second option is better because it is always available regardless of the use of the parameter.
I think that this solution will make it possible to diagnose the action script in the process of writing, and clearer communication of the results on the forum the discussion.
I greet
mlipok
Attachments (0)
Change History (8)
comment:1 by , 12 years ago
comment:3 by , 12 years ago
mlipok,
Just to check I understand correctly: you are asking for 2 buttons on the dialog.
One will return this:
Row |Col 0|Col 1|Col 2|Col 3|Col 4|Col 5
[3]|Item 0|Item 1|Item 2|Item 3|Item 4|Item 5
And the other will return just this:
Item 0|Item 1|Item 2|Item 3|Item 4|Item 5
Am I right?
M23
comment:4 by , 12 years ago
usign
_ArrayDisplay[4].au3
as a example
now using existing button is that:
[0]|JPM|Valik [1]|Holger|Cyberslug [2]|Jon|Nutster [3]|Larry|JdeB [4]|Jeremy|Tylo
I propose something like that
Row|Col 0|Col 1 [0]|JPM|Valik [1]|Holger|Cyberslug [2]|Jon|Nutster [3]|Larry|JdeB [4]|Jeremy|Tylo
This will be even more useful by using a parameter $sHeader
After re-consideration, may simply change the current results of action, the "Copy Selected" according to the proposed amendment, so without introducing a new parameter, and without the new button.
comment:5 by , 12 years ago
| Milestone: | → 3.3.9.23 |
|---|---|
| Owner: | set to |
| Resolution: | → Completed |
| Status: | new → closed |
Added by revision [9192] in version: 3.3.9.23
comment:8 by , 12 years ago
I followed this thread.
The indicated proposed amendment exhausted my feature request.

"please consider adding a new secondary key."
sorry for my vocabulary
I mean:
"please consider adding a new secondary button."