From: Tom B. (Tehom) <te...@pa...> - 2013-05-09 19:49:52
|
> On 05/08/2013 10:32 AM, Aere Greenway wrote: > >> >> It would be nice to have the same capability in the matrix editor. >> Maybe >> you already do, but I don't know how to use it. > [...] > I didn't want to deal with the Matrix Editor because I've never used it > and know nothing about it. I shy away from making modifications in > unfamiliar territory, as it's too easy to break something and never know > it. The matrix editor mirrors the Notation editor in many ways. I've generally found that when I write something for Notation, the code for Matrix is almost exactly the same, just all the names refer to different things. Like NotationWidget -> MatrixWidget, NotationView -> MatrixView, etc. In fact, they mirror each other so much that I dream of moving the duplicated code to a common base class, adding virtual functions as needed. I fear to make such a big structural change, though, even though it looks harmless. > My use of Rosegarden is probably atypical. Rather than using Rosegarden > to capture a midi performance, I begin with Rosegarden's Notation Editor > and end up with a pseudo performance. Any fixes or modifications I > propose are usually a direct result of my atypical experience with > Rosegarden. Sounds much like how I use it. I originally thought I'd be doing more MIDI capture, but I found I was re-editing my performance in such detail that I could more easily just enter stuff from the computer keyboard. Tom Breton (Tehom) |