pelado

I've been updating my abstraction p.storage, a utility for pattrstorage, and

have come across some issues with pattrstorage that I can't fix. I'm not

sure if they are bugs or simply that I'm missing some solution. An example

patch is below and the main points are the following:

- I get an error message "cannot set name of locked slot" when locking a

- I get an error message "no parent patcher found" when using the locate

- When deleting a preset, I am left with an undefined slot that I can't

- The client window allows editing of the active and priority settings of

clients, but there is no similar method for editing the lock setting;

- The client window does have a box to edit interp settings for clients,

but I can't get it to work as expected and settings are not changed.

Any insights into how to remedy these points is appreciated.

Is there a place on the cycling website where we can see all pending bug

fixes for the next release of Max 5? I know about the page that shows what

has been fixed. It would be helpful if there was such a page as trying to

track down if something has been reported already is not necessarily an easy

I've been updating my abstraction p.storage, a utility for pattrstorage, and
have come across some issues with pattrstorage that I can't fix.  I'm not
sure if they are bugs or simply that I'm missing some solution.  An example
patch is below and the main points are the following:

   - I get an error message "cannot set name of locked slot"  when locking a
   preset that has a slotname;
   - I get an error message "no parent patcher found" when using the locate
   message for a pattr is in a subpatch;
   - When deleting a preset, I am left with an undefined slot that I can't
   get rid of;
   - The client window allows editing of the active and priority settings of
   clients, but there is no similar method for editing the lock setting;
   - The client window does have a box to edit interp settings for clients,
   but I can't get it to work as expected and settings are not changed.

Is there a place on the cycling website where we can see all pending bug
fixes for the next release of Max 5?  I know about the page that shows what
has been fixed.  It would be helpful if there was such a page as trying to
track down if something has been reported already is not necessarily an easy
task.

some-pattrstorage-issues-in-max-5

Quote: pelado wrote on Sun, 08 June 2008 13:44

----------------------------------------------------

> I've been updating my abstraction p.storage, a utility for pattrstorage, and

> have come across some issues with pattrstorage that I can't fix. I'm not

> sure if they are bugs or simply that I'm missing some solution. An example

> patch is below and the main points are the following:

> - I get an error message "cannot set name of locked slot" when locking a

> - I get an error message "no parent patcher found" when using the locate

> - When deleting a preset, I am left with an undefined slot that I can't

> - The client window allows editing of the active and priority settings of

> clients, but there is no similar method for editing the lock setting;

> - The client window does have a box to edit interp settings for clients,

> but I can't get it to work as expected and settings are not changed.

Thanks for the excellent bug report & example patch -

Quote: pelado wrote on Sun, 08 June 2008 13:44
----------------------------------------------------
> I've been updating my abstraction p.storage, a utility for pattrstorage, and
> have come across some issues with pattrstorage that I can't fix.  I'm not
> sure if they are bugs or simply that I'm missing some solution.  An example
> patch is below and the main points are the following:
>
>    - I get an error message "cannot set name of locked slot"  when locking a
>    preset that has a slotname;

>    - I get an error message "no parent patcher found" when using the locate
>    message for a pattr is in a subpatch;

>    - When deleting a preset, I am left with an undefined slot that I can't
>    get rid of;

>    - The client window allows editing of the active and priority settings of
>    clients, but there is no similar method for editing the lock setting;

>    - The client window does have a box to edit interp settings for clients,
>    but I can't get it to work as expected and settings are not changed.

Thanks for the excellent bug report & example patch -
jb


>Is there a place on the cycling website where we can see all >pending bug

>fixes for the next release of Max 5? I know about the page that >shows what

>has been fixed. It would be helpful if there was such a page

No - this information is not currently available. Right now - given the amount of work being done on bugfixing, and the many different ways that bugs are brought to our attention, in many cases the maintenance of such a list is more work than the bug fix itself.

We do however feel that communication like this with our bug reporting users is a very useful thing, and are trying to figure out better ways of making this infomation available. Hopefully in the near future we shall be able to offer some kind of list like this.

For now, as you mention - please refer to

https://cycling74.com/version/version_5_0_3.html

>Is there a place on the cycling website where we can see all >pending bug
>fixes for the next release of Max 5? I know about the page that >shows what
>has been fixed. It would be helpful if there was such a page

Yes, I imagine that you could create a lot of extra work into maintaining a

list like this when the forums seem to cover most of the issues. Although,

it would be useful. I come across some issues that I don't report because I

feel that someone else must already have done so.

Maybe a (relatively simple) user reporting mechanism such as many software

sites use for tracking bugs would be possible? It need only have a few

columns such as status, priority, timescale, and a short one line

description with an attachment? I would find it useful to have some way of

searching for a particular object or facet of Max that appears to be the

Actually, the more I think about it the more I appreciate your dilemma.

Perhaps another solution would be to carry on with the forums as a

reporting system and replacing the fixed bug page with something similar to

the above so that bugs solved quickly can simply be reported as fixed.

Whilst those deemed lower priority or requiring more time could at least be

Although some solution now may be closing the door after the horse has

bolted, if future releases have so many bugs such a system would be really

On Mon, Jun 9, 2008 at 6:05 PM, Andrew Pask wrote:

> >Is there a place on the cycling website where we can see all >pending bug

> >fixes for the next release of Max 5? I know about the page that >shows

> >has been fixed. It would be helpful if there was such a page

> No - this information is not currently available. Right now - given the

> amount of work being done on bugfixing, and the many different ways that

> bugs are brought to our attention, in many cases the maintenance of such a

> list is more work than the bug fix itself.

> We do however feel that communication like this with our bug reporting

> users is a very useful thing, and are trying to figure out better ways of

> making this infomation available. Hopefully in the near future we shall be

> able to offer some kind of list like this.

> For now, as you mention - please refer to

Yes, I imagine that you could create a lot of extra work into maintaining a
list like this when the forums seem to cover most of the issues.  Although,
it would be useful.  I come across some issues that I don't report because I
feel that someone else must already have done so.

Maybe a (relatively simple) user reporting mechanism such as many software
sites use for tracking bugs would be possible?  It need only have a few
columns such as status, priority, timescale, and a short one line
description with an attachment?  I would find it useful to have some way of
searching for a particular object or facet of Max that appears to be the
problem.

Actually, the more I think about it the more I appreciate your dilemma.
 Perhaps another solution would be to carry on with the forums as a
reporting system and replacing the fixed bug page with something similar to
the above so that bugs solved quickly can simply be reported as fixed.
Whilst those deemed lower priority or requiring more time could at least be
registered.

Although some solution now may be closing the door after the horse has
bolted, if future releases have so many bugs such a system would be really
worthwhile.

On Mon, Jun 9, 2008 at 6:05 PM, Andrew Pask  wrote:

>
> >Is there a place on the cycling website where we can see all >pending bug
> >fixes for the next release of Max 5? I know about the page that >shows
> what
> >has been fixed. It would be helpful if there was such a page
>
> No - this information is not currently available. Right now - given the
> amount of work being done on bugfixing, and the many different ways that
> bugs are brought to our attention, in many cases the maintenance of such a
> list is more work than the bug fix itself.
>
> We do however feel that communication like this with our bug reporting
> users is a very useful thing, and are trying to figure out better ways of
> making this infomation available. Hopefully in the near future we shall be
> able to offer some kind of list like this.
>
> For now, as you mention - please refer to
>
> https://cycling74.com/version/version_5_0_3.html
>
> Cheers
>
>
> Andrew
>
>

some pattrstorage issues in Max 5