Community
Participate
Working Groups
Build ID: I20080617-2000 Steps To Reproduce: 1. in the debug view select a variable that is an array (e.g. an array of floats) 2. right click and choose "Copy variables" 3. if array has less than 100 entries you will get something like this: MyArray[0] float 0.066326156 MyArray[1] float 0.042602807 .... However, if your array has more than 100 entries you will get this: [0...99] float [197] float [197] MyArray[0] float 0.066326156 MyArray[1] float 0.042602807 .... MyArray[99] float 0.01544505 [100...196] float [197] float [197] MyArray[100] float 0.042602807 MyArray[101] float 0.015485207 .... More information: If I paste this array into OpenOffice I have to remove manually the lines "[100...196] float [197] float [197]". That can be very annoying if the array has some 1000 entries.
In 3.5, the clipboard will only contain text for the expanded items. We'd really need a special copy operation for this that ignored the "synthetic group" items and copied all array entries.
A simple alternative would be an expand-all action. A view preference could be used to limit the depth of the expand all and avoid a recursive expand.
However, the other part of this request is to get rid of the "[0..99]" entries as well (I think).
In reply to comment #3 There are 2 things that are annoying if your array has more than 100 entries: 1) You have to expand every single set of 100 values manually. 2) After copying and pasting you have to remove all the "[0..99]" entries I would like to have: 1) If I select "Copy variables" on an array variable a dialog pops-up that looks like this: First index to copy: 0 Number of entries to copy: 100 (preferable maximum size of array) The two values should be editable. If you have a look at the CDT plugin there is a debug option to cast a pointer to a fixed-size array. A similar dialog pops-up if you do this. 2) The "[0..99]" entries are omitted for copying if I manually select some array values.
This bug is still valid for platform 4.2
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the stalebug whiteboard tag.
