|
|
Mar 25, 2006 at 1:38pm
scrolling in a patch and detonate issues
Hi,
two things:
1-I am working on a patch in which the user creates new objects (whole audio paths in this case) using the scripting/thispatcher object. Thus, everything is fine if there aren’t many objects in the window. However, if the user decides to create more objects that the window can acomodate, these are not accesible. If I unlock the patch, a scrolling bar appears and then I can access the new objects, but this is not a very neat solution: if I create the program as a standalone application, there is no way of unlocking the patch, and thus no way the user can access the newly created objects…(i havent actually done the standalone yet, but I am guessing…)
2- Is there an equivalent of the info~ object for MIDI files? I am particularly interested in finding out info about imported/read MIDI files into detonate: length, bpm etc. Also, while detonate gets the ‘track’ data from MIDI type 1 files, I dont know where to send this data. noteout and midiout dont have inlets for ‘track’ data…
any suggestions?
Thanks
DP
|
|
|
Mar 27, 2006 at 5:27pm
Hi Dan,
sending “window flags grow, window exec” to thispatcher should do it.
You can also roll your own scroller in js using
this.patcher.wind.scrollto.
cheers, g.
|
|
|
Mar 28, 2006 at 8:30am
thanks Georg!!
Of course! I should have had a good look into thispatcher in the reference manual (ooops)…however, I’d never have guessed the js object.Thanks again
dp
|
