On Tue, Sep 29, 2009 at 3:21 AM, D. Michael McIntyre
wrote:
> Whether the sequencer can cope with this properly or not, I have no idea. It
> does seem like there's some pretty good wiggle room on all of this without
> having to go so far as to support 128th (and possibly 256th) notes outright.
T
On Tuesday 29 September 2009, Chris Cannam wrote:
> The theoretical limit throughout Rosegarden itself, in both Classic
> and Thorn flavours, is 1/3840 note (1/960 of a quarter note).
Ah, OK, that follows, but it conflicts with something or other I had half in
my head that was probably that obso
On Tue, Sep 29, 2009 at 3:09 PM, D. Michael McIntyre
wrote:
> The only thing is if we did want to add 128th and maybe 256th notes, we'd have
> to change whatever the "minimum duration" constant is, and make some follow-on
> adjustments from there. I forget what that's called or where it's defined
Firstly, I recognise that neither the project I'm embarking on (nor I
suspect Jani's project) are critical to release.
I can see that there is a bunch of hook-up work still required on the
control rulers: cut & paste, Controller N (there must be plenty of
others?)
I'd like to get these out of the
2009/9/29 Chris Fryer
>
> I think the main area of overlap will be, as you suggest, in the storage
> of the events in the segment. I want to be able to identify a transition
> when reading a document (and then segment) so that it is modifiable.
> Just producing a stream of regular control events
Le mercredi 23 septembre 2009 00:29:53, D. Michael McIntyre a écrit :
>
> As far as the warning icon itself, I think this situation of mismatched
> clefs or keys or transpositions is not necessarily /!\ level warning
> material. It should probably be more like a /?\ kind of thing, or maybe
> even
On Tue, 2009-09-29 at 20:39 +0100, Chris Fryer wrote:
> I can see that there is a bunch of hook-up work still required on the
> control rulers: cut & paste, Controller N (there must be plenty of
> others?)
Oh yeah, NotationView. Think I'd best get on that!
---
Sorry for my late reply.
Le mercredi 23 septembre 2009 00:45:01, Julie S a écrit :
> Can we avoid using a popup? Is it really necessary? I don't see the use
> of this unless there is a decision to be made. If the only option
> presented is an button "ok" then there is no decision to be made.
L
Dear Yves,
> But please note that this explanatory window will not pop
> up automatically :
Ok. That is good.
> Do you agree to such a feature ?
If the information in the window is dynamic---changes based on the issue that
needs to be resolved. Then use QMessageBox to display it.
If the mes
On Tuesday 29 September 2009, Chris Fryer wrote:
> I'd like to get these out of the way first but am a bit stuck so was
> looking at the transition work.
Oh, I'm sorry. I said something about looking into that, but I took a glance
and then never really thought about it again. I misread whateve
On Tuesday 29 September 2009, Yves Guillemot wrote:
> That said, I possibly misused the word popup.
I don't think it matters much. We all understand what you mean now.
They were thinking you meant something like the old "system timer resolution
is too low" warning dialog that starts EVERY TIM
11 matches
Mail list logo
