Hello Brett, I understand what you are trying to do. I can't claim I understand the deep levels of the realtime computation in RG. But I don't think in every scenario of meter and tempo combination we have msec granularity in RG. I hope that makes sense.
... Anyhow, I did try the eventFInished() signal and got that working here. But I'm still a bit dis-statisfied with it from from a User Interface perspective. THe problem I see is that typing in all of the other boxes perform an auto-recalculation and Rg's granularity is such that updating those boxes does not cause any of the issues we are seeing in the msec box. So I think the best approach is still to auto-recalculate that box as well. Here is my next thought. Whenever we type in msec box or use the up and down arrows for the box, we start (or restart) a one shot timer (say set it for 1500 msec). When the timer fires (time elapsed) we perform the recalculation using the value in the msec box. Also If the msec box looses focus, we kill the time, and perform the recalculation. ... Any thoughts about that approch? This would give users time to type in the box without their entries getting rewritten as they type. Sincerely, Julie S. --- On Sat, 2/5/11, Brett McCoy <[email protected]> wrote: > From: Brett McCoy <[email protected]> > Subject: Re: [Rosegarden-devel] Minor bug in TimeWidget > To: "Julie S" <[email protected]> > Cc: "rosegarden-devel" <[email protected]> > Date: Saturday, February 5, 2011, 2:24 PM > On Sat, Feb 5, 2011 at 1:30 PM, Julie > S <[email protected]> > wrote: > > > I guess we could just not recalculate in this > scenario, and just let people they are actually getting 123 > msec or 124 msec (when in reality they are not). > > > > ... > > > > I think as long as the Sequencer or nothing else is > breaking, I think we should just let people type what they > want in this box and not bother with adjusting it to the > "real time." > > The issue is I am using markers in RG to align with makers > I have set > in Ardour to synch to specific frames in a video (using > xjadeo). > Sometimes the markers don't hit right on a beat so I use > Ardour's > seconds & milliseconds clock to figure out the marker's > position and > this was when I discovered this curious behavior. If I want > to input > 467, I have to type 578. > > Another option might be to have a video synch value (like > 24 fps or > 29.97 or whatever) and be able to enter the frame value > directly. > > -- > Brett W. McCoy -- http://www.electricminstrel.com > ------------------------------------------------------------------------ > "In the rhythm of music a secret is hidden; If I were to > divulge it, > it would overturn the world." > -- Jelaleddin Rumi > ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
