Hi all !

I 'm use to create boxes automatically with this method:

[obj 200 50 spigot(
|

Is there a way to delete it, or other boxes automatically?
Thanks a lot for your precious help !!

hey,
I always did that with the mouseoperations. The annoying thing about this (to me) is that one has to make the window visible and invisible again. I wonder how much CPU-time that superfluous action takes..
Does anyone know if there is a way without making it visible?!
Creating single objects or deleting the whole canvas works without it being visible...

I tried the find-stuff. It works, but the pd-console prints
"consistency check failed: sys_decodedialog: testabs"
Anyone with the same message?! And what does that mean...
And, dwan do you know what that number (0/1) behind the message does???

Now did someone work with pointers & scalars?! I'd be interested if that works as well with that find-stuff...
...the funny thing is that a pointer actually is something like a name, but I guess it's not working anyways...

Btw. you can find some documentation in the help-browser: "0.all_msg.pd"

In Pd-extended 0.43, there is the new iemguts library which has an object called [canvasdelete]. It allows you to delete an object by its index (creation order), and you don't need to have the window visible.

@Flipp said:

Btw. you can find some documentation in the help-browser: "0.all_msg.pd"

It seems that the file you are referring to is not in vanilla package.

I found all these tricks by crawling through the pd-list with judicious keywords and infinite tenacity.

About the number following [find<, i found that [find< behaves differently on windows and linux, so you've got to use what works best for you on each platform, i don't remember...

Dwan, could you explain what the three zeros after the x-y coordinates mean, in the mouse command? I checked the 0.all_msg.pd but didn't really understand.

Well, i don't really remember. Guess i've just followed Manuals/pd-msg/1.msg_and_patch/ ...

Anyway, the help files are not very helpful as they don't state why the message ends with three "0".

from memory, the zeroes at the end had something to do with Graph-on-Parent. But i may have a bad memory...