From: D. M. M. <mic...@ro...> - 2009-10-29 22:39:06
|
On Thursday 29 October 2009, Emanuel Rumpf wrote: > @Chris F. Will it be possible to add custom number controllers (to > select the midi-ctrl. number)? It already is. Studio -> Manage MIDI Devices -> Controllers... Let's say you want to add controller 53 called "Distort." Click Add. Set up your controller (name "Distort" number 53 etc.) and then the next time you open a matrix or notation view, the new controller will show up on the list of available rulers to choose from. (In theory. In practice when I tried to go through this just now, I crashed trying to create the new controller.) > Do you plan to (or already do) support fine tune (LSB) controller messages > ? I'll leave that to somebody else. I don't know what you're talking about. > @ Chris C. , you made the dialogs "delete on close". > But that means, they loose their status too. (size,position,selected > items,.. ) Is it worth that? Where would be the right place to store such > data ? In QSettings ? They definitely need to be delete on close. We had a ton of crashes related to this. QSettings is the way to go indeed. All major editors already store last position and size in a special settings group, so there is code to follow if you are interested in implementing this elsewhere. You implement a custom closeEvent() method for this purpose, which could also be used to store any other settings. I've also found a few things here and there that read from settings (settings.value() ) but never actually *write* any settings (settings.Value() ) back out. I fixed one or two, but there are probably more to do. Please note that if you do wish to store additional dialog-specific settings (see PresetHandlerDialog for an example) beyond the window position data, please use appropriate config groups to do it. > The position line/pointer/cursor doesn't move on playback anymore. > (Only when pressing <back> while playing) Where? I assumed you were talking about the matrix (from context) and everything seems to check out there as far as I see. > The first playback-device sometimes gets arbitrarily renamed (without > user interaction), especially when pressing the refresh button in the > DeviceManager. I haven't seen this. In practice I've found the refresh button is not normally needed, incidentally. > 2 backtraces: > > --------------------------------------------------------------------------- >------------------------ There are still/again crashes when importing files: Leaving that for Chris Cannam when he gets back from (another, ugh!) trip away. -- D. Michael McIntyre |