Es geschah am Wednesday 18 March 2009 als Luis Garrido schrieb: > > 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 :-)
So, then I propose to change in src/engines/InstrumentManager.h the current method: virtual void LaunchInstrumentEditor(instrument_id_t ID) throw (InstrumentManagerException) = 0; to : virtual InstrumentEditor* LaunchInstrumentEditor(instrument_id_t ID) throw (InstrumentManagerException) = 0; I could do that change within the next days. Should be done in couple minutes. That'll be suficient for you? > 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. Of course you can dynamic_cast the pointer to your class. CU Christian ------------------------------------------------------------------------------ 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
