geraldg@gmx.de

I got the following problem! Always when I try to use a while loop 

max crashes imemdiately! For example, when i have a proces that should run as long as a Max-toggle is ON, and stop when it is OFF.

It is only working, when I create a java thread, and say Thread.sleep (some mills)

Has anybody an idea how to fix it, or is a java loop just too fast for max?

It seems to be the same problem, when trying to build a loop within max itself.. :-(

I got the following problem! Always when I try to use a while loop 
max crashes imemdiately! For example, when i have a proces that should run as long as a Max-toggle is ON, and stop when it is OFF.
It is only working, when I create a java thread, and say Thread.sleep (some mills)

Has anybody an idea how to fix it, or is a java loop just too fast for max?
It seems to be the same problem, when trying to build a loop within max itself.. :-(

java-do-while-loop

On May 11, 2007, at 11:44 AM, Gerald wrote:

> I got the following problem! Always when I try to use a while loop

> max crashes imemdiately! For example, when i have a proces that 

> should run as long as a Max-toggle is ON, and stop when it is OFF.

> It is only working, when I create a java thread, and say 

> Has anybody an idea how to fix it, or is a java loop just too fast 

> It seems to be the same problem, when trying to build a loop within 

Sounds like you're trying to perform some sort of loop in the main 

thread which is waiting for other main thread execution to stop. This 

won't work since the application can never process the toggle off-- 

This needs to be in a separate thread or else the state of 

this.toggle will never change. Sleeping doesn't let other parts of 

the same thread work, it puts the entire thread to bed, only letting 

*other* threads work. The application hasn't crashed in this 

instance, it's just waiting for input it can never get, because it 

won't let the portion of the program which receives input ever run.

If this is confusing, I'd suggest reading more on threads. A book I 

cite a lot ("Modern Operating Systems") isn't Java specific, but it 

has some good info on threading. In fact one of the freely available 

chapters is on Threads. See the "Sample Sections" from the link 

http://www.prenhall.com/divisions/esm/app/author_tanenbaum/custom/mos2e/

You can also use a qelem (Queue Element) to schedule low priority 

callbacks to perform asynchronous operation within a single thread. 

Some C related info (which shouldn't be that hard to map to a java 

mxj implementation) is in this discussion:

https://cycling74.com/forums/index.php?t=msg&goto=32275

> I got the following problem! Always when I try to use a while loop
> max crashes imemdiately! For example, when i have a proces that  
> should run as long as a Max-toggle is ON, and stop when it is OFF.
> It is only working, when I create a java thread, and say  
> Thread.sleep (some mills)
>
> Has anybody an idea how to fix it, or is a java loop just too fast  
> for max?
> It seems to be the same problem, when trying to build a loop within  
> max itself.. :-(

Sounds like you're trying to perform some sort of loop in the main  
thread which is waiting for other main thread execution to stop. This  
won't work since the application can never process the toggle off-- 
i.e. in something like the following:

while (this.toggle)
{
	getfreaky();
	sleep(666);
}

This needs to be in a separate thread or else the state of  
this.toggle will never change. Sleeping doesn't let other parts of  
the same thread work, it puts the entire thread to bed, only letting  
*other* threads work. The application hasn't crashed in this  
instance, it's just waiting for input it can never get, because it  
won't let the portion of the program which receives input ever run.

If this is confusing, I'd suggest reading more on threads. A book I  
cite a lot ("Modern Operating Systems") isn't Java specific, but it  
has some good info on threading. In fact one of the freely available  
chapters is on Threads. See the "Sample Sections" from the link  
below, if interested.

You can also use a qelem (Queue Element) to schedule low priority  
callbacks to perform asynchronous operation within a single thread.  
Some C related info (which shouldn't be that hard to map to a java  
mxj implementation) is in this discussion:

java do-while loop