> On 4/12/2012 3:23 PM, Tom Breton (Tehom) wrote:
>> Clearly something is drastically wrong and varies by setup. I just
>> can't see how.
>
> Got it...
Wonderful! That is a truly impressive piece of debugging, Ted.
> 1. Get rid of the ChannelInterval static constants. Just use the
> RealTime ones directly.
>
> 2. Use #defines.
>
> 3. Initialize the ChannelInterval static constants the same way the
> RealTime constants are initialized.
>
> I would be inclined at this point to use #3 and add a comment to
> preserve a link to the RealTime constants:
>
> // Same as RealTime::beforeMaxTime
> const RealTime
> ChannelInterval::m_latestTime(std::numeric_limits<int>::max(),0);
>
> This at least gives you what you want even if there is a bit of a
> double-maintenance headache (however unlikely) lurking.
(3) seems the best to me too. Other than zeroTime, those constants were
only in RealTime to make them visible in case of re-use. So other than
zeroTime, I'd just move them.
Tom Breton (Tehom)
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
