how to delete a dict from memory ?

Nov 8, 2012 at 4:13pm

how to delete a dict from memory ?

Hi,

it may be something obvious, but I could not find the answer in the documentation, nor in the forum :
“how to delete completly a dict ?”
I mean, not only removing its content with a “clear” message, but also destroying the reference so that it does not appear anymore in the dict list when you query it with “getnames”.
Even if I close the patch containing my dict instances and creating a dict objet alone in a new patch, it will still reference all the dict from my previous patch, which remained in memory.

thanks for any hint / method to achieve that.

#65143
Nov 8, 2012 at 11:34pm

bump ! bump ! bump !
nobody can answer me ? Cycling74 fellows, please help !

(or at least tell me : “No, that’s not possible at the moment. Maybe in a future release” … so that i know … )

#234815
Nov 12, 2012 at 4:54pm

ok, to make my point clear, I made a small example patch below …
can anybody answer ?

– Pasted Max Patch, click to expand. –
#234816
Nov 12, 2012 at 6:01pm

I’ve encountered the same in earlier versions of Max 6. Haven’t tried recently, though.

#234817
Nov 12, 2012 at 8:06pm

Thanks for your reply, Peter.
It seems like it could just be a missing command to the dict object… something like an “erase [DictName]” command.
C74 team ?

#234818
Nov 20, 2012 at 8:25pm

I repost the reply from C74 support in case anyone face the same problem :

There is currently no way to delete a dictionary completely from a patcher. There is a way to do it from JS, using the freepeer() method.
You can use freepeer if the dicts were created in JS, but if they are a max dict box, then there will always be a dictionary present. Possibly randomly named. In general we’d recommend that you manage your own list of dictionaries to present to the user rather than relying on the global dictionary list for presenting a user interface. There’s nothing that we guarantee about using that global list of named dictionaries for such purposes.

#234819

You must be logged in to reply to this topic.