Hi Menno,

I do sort of like that idea of putting the upper and lower boundary into one diagram. In practice it often can happen that you are not sure, if the lower boundary already crossed the upper boundary. So I'd prefer your suggestion, Menno.

There is only one situation thinkable where one diagram would be a disadvantage: If you have to set the values in a very high range, lets say about 10000 and the lower limit in a range of lets say 0 - 1.
The graphs would then be miles apart and/or the resolution would be poor.

To cure this, the min/ max values for each graph could be maintained, so that, if set to similar ranges, the graphs could be easily compared and if set to totally different ranges, the graphs could still reside in the same diagram.

So, with this feature, two graphs in one diagram would serve all desires. What do you think, Steven?

All the best,

Jan Jacob

Am 07.05.2008 um 08:12 schrieb menno:

i forgot to say:
how about one graph where you can set the upper and the lower boundary? It
is more clear to see what will happen in time and it will make clear that a
lower boundary that is unintentionally set a a higher value than the high
boundary will be spotted.


View this message in context: http://www.nabble.com/JMask-Beta-tp17030688p17098044.html
Sent from the Csound - Blue - User mailing list archive at Nabble.com.

This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
Bluemusic-users mailing list

sound         |         movement          |          object         |          space

sonic architecture       |        site: http://www.sonicarchitecture.de  

spatial electronic composition     |    2nd order ambisonic music