John Labenski <jlaben...@...> writes: > > I'm sorry, this is not something that I have time or interest in. I > recommend that if you are serious about this that you look at the > wxWidgets wiki about building wxWidgets, then move to building wxLua, > and finally wxMidi. Once you have those three built you can write a > binding file for wxMidi, like the ones the wxLua's binding directory, > and generate the C/C++ code to be compiled into a library to build > into wxLua. Yes, it will be a fair amount of work.
Well, now you put it like that it sounds like a rediculous solution. If everyone who needed to drive had to build big chunks of the car, no-one would go anywhere! If it's too much for the person best placed to do it, then it's obviously too much for anyone else. Besides, that degree of work is absurd if it's possible to use a small program on a RAM drive to read a file, saved to same RAM drive, to get the data out. The program I found comes very close to this. I'll ask the maker, if I can find him, if he's willing to make a copy that has no GUI, takes specs from INI file, perhaps. With a separate executable, there's no need to worry about keeping up with CVS and all that. This really ought to be doable without having to devote a chunk of life to reinventing a wheel. I thought that wxMIDI was supposed to BE that wheel anyway, yet you make it sound like I'd be better off designing from scratch. It seems that it might be so, learning enough C to write a tiny app to read from saved file and port to and from MIDI, forget about trying to integrate closely with a system whose writer(s) really don't want to know. You speak of MIDI as if I mentioned music piracy or something. It really seems to put your back up somehow, abnd I really don't know why. ------------------------------------------------------------------------------ _______________________________________________ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
