yeah, thats true. i'm developing a synthesizer, and i was originally planning on separating the synth core from the gui, so you could choose if you need to gui or not. it occured to me that i heard sometime ago that hidden gui objects dont impact the cpu performance. so it would be easier for me to develop it as one abstraction, if you need the gui, popup the gui window, other wise dont. of course this hinges on my understanding that hidden gui objects dont impact performance.
btw, its polyfonic now adn has a functioning gui editor for the synth parameters... i'll be releasing 0.1 pretty soon now once i work out a few of the really obnoxious bugs :)
-josh
pix wrote:
why have gui objects if they are hidden?
if you plan on opening/closing subpatches during a performance, it invariably causes hiccups for me.
pix.
On Fri, 30 May 2003 10:42:51 -0700 Josh Steiner josh@vitriolix.com wrote:
Problems arise if you use and display too many builtin graphical objects.
Guenter
i've been working on some heavy graphics patches, do you know it will matter if i have all my GUI stuff "hidden" in a subpatch? i'm hoping that all the gui objects wont hamper performance when they are not displayed.
-- ____________________________________________________ independent u.s. drum'n'bass -- http://vitriolix.com
PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list