02-05-2007 08:42 AM
02-05-2007 09:03 AM - edited 02-05-2007 09:03 AM
02-05-2007 09:10 AM
In my opinion, this is simply a small bug in the documentation and you should not be able to change the size of the function.
Think about the following case: You tell it to delete row #2 and row #4. Is row #4 the original #4 or #4 after you've deleted #2 (i.e. what was originally #5)? To avoid having to deal with this, you simply can not delete at more than one index and the documentation itself doesn't even hint that you can. The "index n-1" part actually refers to the number of dimensions that the array has.
Basically, that resizing arrow should simply not be there.
02-05-2007 03:15 PM
Hi tst,
Yes, your explanationmakes sense. This is why I posted this example and pointed to the info in the Context Help.
I was surprised not being able to do it. I was more curious at how it could be done!! 😮 Thanks..
Now, should this be reported as a documentation bug?
RayR
02-05-2007 03:28 PM
Thinking about this some more, I'm not entirely sure it is a bug, since the function does resize, simply without your control.
@JoeLabView wrote:
Now, should this be reported as a documentation bug?
02-05-2007 03:31 PM
02-06-2007 06:53 AM
Yes, this is what I ended up doing. Especially since time is of essence.
However, I do want to play with the power of vi's with arrays, in ways to avoid using loops. (a nugget in the making) 🙂
02-07-2007 09:32 PM
02-08-2007 08:16 PM