That's just a matter of creating a single number box and connecting its

output to [s $0-offset].

Well, there's bounds checking, too-- the point is it's all just a Pd patch

so you're unlikely to crash Pd by revising the functionality. Plus the barrier

to entry is much lower than the small number of people who can untangle

garray-related spaghetti code.

-Jonathan

On Friday, November 13, 2015 4:00 AM, katja <katjavetter@gmail.com> wrote:

That looks good Jonathan. In current array list view the entries are grouped per 1000 and arrows let you switch groups. For 'large' arrays (say one second of audio samples) this is inconvenient. Maybe your patch approach could even provide a better solution, like the option to select a specific range.

There's also method 'arrayviewclose' which I sometimes (ab)use to close a list view from within a patch. You don't want to try update an audio array list view in real time!

On Fri, Nov 13, 2015 at 1:32 AM, Jonathan Wilkes <jancsika@yahoo.com> wrote:

I don't know. Something like this with the guts hidden?

I didn't do the hard stuff, like handling out-of-bounds elements if the
array isn't a multiple of ten-- it's just a prototype.

So, in that method you and katja are abusing, I can forward the arrayname
as well as the current $0 count. Then I can open the patch and immediately
send a message to the relevant $0- receiver, and the patch will populate the
value table accordingly.

And then I can get rid of all the arraylistview C/GUI code that's scattered about.

-Jonathan

On Thursday, November 12, 2015 4:55 PM, Matt Barber <brbrofsvl@gmail.com> wrote:

A Pd patch with what in it?

On Thu, Nov 12, 2015 at 4:21 PM, katja <katjavetter@gmail.com> wrote:

On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes <jancsika@yahoo.com> wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?

Could be OK if the list is editable, like current array list view.

Katja