From: Florian J. <fl...@wi...> - 2013-08-10 10:16:58
Attachments:
signature.asc
|
Hi, my changes require altering the Python support. I ran through MusE and changed all "ModifyPart" or "ChangePart" by more specific "ModifyPart{Length,Tick,Name}". My goal is that when changing a Part, the Part pointer may never change! newpart = oldpart->clone(); newpart->setLenTick(1337); song->cmdChangePart(oldpart,newpart); becomes song->cmdChangePartLength(oldpart, 1337); However, also the pyhton bindings rely on ModifyPart, and i have absolutely no experience with writing python-bindings. Who wrote this? Can you please explain me how it basically works? And, possible problem: There will be no ModifyPart any more. Will this require fixing all python scripts (are there many?), by instead calling ModifyPartTick etc? Or can we even do a little compatibility hack? Greetings flo |
From: Robert J. <spa...@gm...> - 2013-08-13 08:10:27
|
Hi Florian, 2013/8/10 Florian Jung <fl...@wi...>: > Hi, > > my changes require altering the Python support. > > I ran through MusE and changed all "ModifyPart" or "ChangePart" by more > specific "ModifyPart{Length,Tick,Name}". My goal is that when changing a > Part, the Part pointer may never change! > > newpart = oldpart->clone(); > newpart->setLenTick(1337); > song->cmdChangePart(oldpart,newpart); > > becomes > > song->cmdChangePartLength(oldpart, 1337); > > > However, also the pyhton bindings rely on ModifyPart, and i have > absolutely no experience with writing python-bindings. > > Who wrote this? Can you please explain me how it basically works? These were mostly written by Mathias Gyllengahm, I might have done some bits, can't recall. > > And, possible problem: There will be no ModifyPart any more. Will this > require fixing all python scripts (are there many?), by instead calling > ModifyPartTick etc? > > Or can we even do a little compatibility hack? I don't think you need to fear the python scripting. To my knowledge there are no scripts for this interface, it was a hack for trying to extend and remote control muse, the support should not be enabled unless EXPERIMENTAL is enabled in the configuration. As for scripting you may be thinking of the scripts in muse2/share/scripts, these are mostly written in python by myself but can be created in any language as they use a simple protocol defined in muse2/share/scripts/README.txt, this is all implemented separately from the python bindings. Regards, Robert |