Guillaume Evrard

is there a way to make an object to remove itself ?

if you try to self-call the remove method for the maxbox associated to your class, it makes max to crash.

i tried to call a static method located somewhere in my package from the object i want to delete, but this is the same problem.

is there a way to make an object to remove itself ?
if you try to self-call the remove method for the maxbox associated to your class, it makes max to crash.
i tried to call a static method located somewhere in my package from the object i want to delete, but this is the same problem.

autodestruction

Well, assuming that trying to get an object to delete itself is always 

going to make max eat its own tail and crash, couldn't you just send a 

script message out to [thispatcher] to remove the box?

Why do you want this, if you don't mind me asking?

> is there a way to make an object to remove itself ? if you try to

> self-call the remove method for the maxbox associated to your class,

> it makes max to crash. i tried to call a static method located

> somewhere in my package from the object i want to delete, but this is

> G. _______________________________________________ java-dev mailing

Well, assuming that trying to get an object to delete itself is always 
going to make max eat its own tail and crash, couldn't you just send a 
script message out to [thispatcher] to remove the box?

guillaume wrote:
> Hi,
>
> is there a way to make an object to remove itself ? if you try to
> self-call the remove method for the maxbox associated to your class,
> it makes max to crash. i tried to call a static method located
> somewhere in my package from the object i want to delete, but this is
> the same problem.
>
> is there a solution?
>
> G. _______________________________________________ java-dev mailing
>


On 12 avr. 07, at 13:20, guillaume wrote:

> is there a way to make an object to remove itself ?

> if you try to self-call the remove method for the maxbox associated 

> i tried to call a static method located somewhere in my package 

> from the object i want to delete, but this is the same problem.

I didn't test that in java, but in javascript, i've been able to do 

that, by using a clock. The clock thread seemed to be freed cleanly 

> is there a way to make an object to remove itself ?
> if you try to self-call the remove method for the maxbox associated  
> to your class, it makes max to crash.
> i tried to call a static method located somewhere in my package  
> from the object i want to delete, but this is the same problem.
>
> is there a solution?

I didn't test that in java, but in javascript, i've been able to do  
that, by using a clock. The clock thread seemed to be freed cleanly  
after that.

well, i'm creating a toolbox that constructs parts of patchs automatically with native max objects. Once this is done, i would like to remove the mxj object in charge of the construction, in order to have a clean patch containing only the result of the construction process.

> I didn't test that in java, but in javascript, i've been able to do 

> that, by using a clock. The clock thread seemed to be freed cleanly 

new MaxQelem(
   new Executable()
   {
     public void execute()
     {
       getMaxBox().remove();
     }
   }
).set();

> I didn't test that in java, but in javascript, i've been able to do 
> that, by using a clock. The clock thread seemed to be freed cleanly 
> after that.


On 12 avr. 07, at 18:13, Owen Green wrote:

> Just tried in Java, seems to work fine:

> Just tried in Java, seems to work fine:
>
> new MaxQelem(
>   new Executable()
>   {
>     public void execute()
>     {
>       getMaxBox().remove();
>     }
>   }
> ).set();

Autodestruction