> Generally I do not think about the checker dialog as an editor, for me
> it's just something that indicates issues in the content of the notation
> editor. It does not change the music (ok, technically yes, because it
> sets/resets a property of an event, but it does not really change what is
> played).
>
> Also the parent of the dialog is the notationView, so if the notation
> editor is closed, the checker dialog is closed as well. The dialog gets
> the this-pointer of the notationView upon creation, so this pointer is
> always valid as long as the dialog exists.
> If the users starts the search, all information is built from that pointer
> (list of staves, list of segments). So during search the content that the
> checker uses is the current content of the notation editor.
I see. I wrongly assumed that this was global, across all segments. It's
clearer now. Good plan, too.
So I still haven't really answered your question about how information
gets from dialogs (or really from the gui) out to commands. When you said
"dialog", I thought you meant the kind of dialog we have that triggers one
command and disappears.
Now if I understand, you want this dialog (or editor) to stay open for
many commands. That seems to me more like the editors than the existing
dialogs. If you like, you can see everything that hosts commands in
data/rc/. In addition to the editors, there are other things like
inserters, erasers and rulers, but they seem even less relevant. So
that's all the ways that Rosegarden issues commands.
It's a lot of work to make a new editor, which is why I hesitate to
recommend it, but if you want to go that route, it may be easiest to start
by copying the tempo or eventlist editor, because they are the smallest.
> So, if the user really changes the segments in the notation editor during
> parallels checking, he/she just has to click on restart to get an updated
> list of parallels. Again, I think this effort is tolerable.
Sounds reasonable.
> Advantage is
> that most of the code is encapsulated in the dialog and there not so much
> interference with the source of notationView (should make maintenance
> easier)
Again, sounds reasonable.
Good luck!
Tom Breton (Tehom)
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
