>
>> On 29.03.2015, at 03:09, Tom Breton (Tehom) <te...@panix.com> wrote:
>>
>>>
>>
>> When it returns, we check whether it succeeded or was aborted. If it
>> succeeded, we're still not done. In fact, we haven't *done* anything at
>> that point.
>>
>> Now we extract the values from the dialog and pass them to a command,
>> which is another object. That has to be executed too, but then you're
>> done.
>>
>> There are all sorts of exceptions and variant cases around, so don't
>> take
>> this as an absolute rule of how RG always does things.
>
> Ok, thanks for the info. I will have to think about that, as the checker
> stays open all the time until the users closes it.
> This reflects the intended workflow as I would like it.
That will probably be hard.
The things that stay open until they are closed are editors, like, the
notation editor.
Getting an editor to talk to another editor is tricky. Editors can work
on the same segment simultaneously, but they do it indirectly: each one
sees and reacts to all the changes, but they typically don't tell each
other to do anything. Co-ordinating two editors sounds tricky.
It might make more sense to store the parallels in some global object and
dispatch commands that navigate them, like "Next Parallel", in the
notation editor itself. That's probably easier than co-ordinating two
editors, or getting a dialog to stay open across commands without
problems. That's what I'd recommend.
Now I can't help thinking, "What about parallels in segments that the
notation editor isn't visiting?" I suspect you have a plan to deal with
those.
Afraid I can't help with Lilypond.
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
Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
