Es geschah am Wednesday 18 March 2009 als Christian Schoenebeck schrieb:
> 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 InstrumentEdito
Es geschah am Wednesday 18 March 2009 als Luis Garrido schrieb:
> Perfect, I am not very familiar with pointer wizardry and I read
> somewhere that you had to enable rtti in your compiler for this to
> work, but that's probably the default setting.
Yes, RTTI is enabled by default with g++, no need
> 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?
>
Sounds about good, thanks a lot.
> Of course you can dynamic_cast t
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
> > applicati
> 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 a
Es geschah am Tuesday 17 March 2009 als Luis Garrido schrieb:
> Correct me if I am wrong. As I see it, the way to spawn an editor from
> an app is:
>
> - Create a plugin dll and install it at the plugin dir in place of
> gigedit, since only one single editor is supported.
> - In the main applicatio
