> Well, if we would extend the API by returning back a pointer to the launched
> instrument editor, there would be no need for such an additional message
> passing mechanism. Because you could implement that in your application
> internally, right? Would that be sufficient for you?

Great that we are in the same page now :-)

I think so, as long as I can dynamic_cast it to my derived class so I
can use my extended API. Then there's indeed no need to extend the
base class to support messaging.

> So don't hesitate to criticize things! Either the criticizms are justified,
> then we try to solve the problem, or we tell you why we think its not
> justified.

Excellent, I can identify with that!

Luis

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

Reply via email to