Thanks again. Can you confirm that a range with onset greater than n-1
should be empty, and not a range with just the (n-1) item? I'm building
some abstractions with these, and I want range behavior to be consistent
with those in the [array] objects.
Thanks!
M
On Fri, Sep 11, 2015 at 7:50 PM,
Yep, that sounds like the correct way to interpret it.
I've attempted a fix, now up on git repo.
Thanks again for flagging this
M
On Sat, Sep 12, 2015 at 08:18:31PM -0400, Matt Barber wrote:
> Thanks again. Can you confirm that a range with onset greater than n-1
> should be empty, and not a
Thanks for the fix in 0.46.7. There are a couple more subtle problems
having to do with bounds checking (one of which may be there by design).
Bounds checking occurs in the function array_rangeop_getrange() starting
line 536:
firstitem = x->x_onset;
if (firstitem < 0)
firstitem =
Thanks.
I meant to say that there was the same problem in [array min], but you
probably caught it in your fix.
Best,
Matt
On Fri, Sep 4, 2015 at 7:19 PM, Miller Puckette wrote:
> Yep... thanks. Fixed in git - may take some time for me to get out a new
> compiled version
Yep :)
M
On Fri, Sep 04, 2015 at 07:46:30PM -0400, Matt Barber wrote:
> Thanks.
>
> I meant to say that there was the same problem in [array min], but you
> probably caught it in your fix.
>
> Best,
>
> Matt
>
> On Fri, Sep 4, 2015 at 7:19 PM, Miller Puckette wrote:
>
> >
Hi list,
I've been playing around with the new(ish) [array] object suite in vanilla
0.46.6. Forgive me if this is already a known issue, but it looks like the
min and max arguments aren't working properly.
The second inlet (setting the number of points to search) works as
expected. The first
Yep... thanks. Fixed in git - may take some time for me to get out a new
compiled version (other stuff to fix too :)
M
On Fri, Sep 04, 2015 at 05:51:15PM -0400, Matt Barber wrote:
> Hi list,
>
> I've been playing around with the new(ish) [array] object suite in vanilla
> 0.46.6. Forgive me if