Hi again, please let me tell you what I did. I implemented a new class "qtractorMidiController" which should do a kind of mapping midi controllers to functions inside of qtractor. I'm pretty sure, that some things I did in the code are more like hacks, than a fine programming. And of course, my implementation is missing a GUI.
Another problem is, that you mentioned that you did you implementation with the MVC pattern. This means, that with my MidiControllerMap i am adding a new controller and view. And as the controller does update the view, a lot of code has to be copied into the MidiControllerMap. I think, one should implement the VIEW with an observer pattern, so that the MidiControllerMap is just another observing view which reacts on changes of the model data. What do you think?
Maybe I should send you my code? Unfortunately I did my changes to the 0.4.1 version and therefore I would have to update it to the 1317 revision. Please let me know, what is the best way for supporting the project.
Hi again, please let me tell you what I did. I implemented a new class "qtractorMidiController" which should do a kind of mapping midi controllers to functions inside of qtractor. I'm pretty sure, that some things I did in the code are more like hacks, than a fine programming. And of course, my implementation is missing a GUI.
Another problem is, that you mentioned that you did you implementation with the MVC pattern. This means, that with my MidiControllerMap i am adding a new controller and view. And as the controller does update the view, a lot of code has to be copied into the MidiControllerMap. I think, one should implement the VIEW with an observer pattern, so that the MidiControllerMap is just another observing view which reacts on changes of the model data. What do you think?
Maybe I should send you my code? Unfortunately I did my changes to the 0.4.1 version and therefore I would have to update it to the 1317 revision. Please let me know, what is the best way for supporting the project.