Hi again. I met a little inconvenience. The plugin must know whether it has been spawned by a master application or not, so in the latter case it can spawn its own GUI.
As things stand now this can be resolved with some negotiation that involves a timeout for the case where the main app is not present. This timeout should be carefully chosen so it won't slow down too much the startup of a standalone plugin (how long should the plugin wait for the main app to make its presence known?) This could be avoided if the plugin knew from the very first moment that it has been spawned at the request of the main app. I think an easy solution would be to modify the following APIs: virtual InstrumentEditor* LaunchInstrumentEditor(instrument_id_t ID) throw (InstrumentManagerException) = 0; to virtual InstrumentEditor* LaunchInstrumentEditor(instrument_id_t ID, void * pUserData = 0) throw (InstrumentManagerException) = 0; and virtual int LinuxSampler::InstrumentEditor::Main(void * pInstrument, String sTypeName, String sTypeVersion) to virtual int LinuxSampler::InstrumentEditor::Main(void * pInstrument, String sTypeName, String sTypeVersion, void * pUserData = 0); What do you think? 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
