On Tuesday 05 August 2003 17:09, Guillaume Laurent wrote:
> On Tuesday 05 August 2003 16:55, Chris Cannam wrote:
> > Guillaume Laurent wrote:
> > > Yes, the sequencerCall() and sequencerSend() methods should be no-ops
> > > if --nosequencer is given.
> >
> > I'm not sure that's entirely true either. I think in most cases
> > we should be taking more care not to call them in the first place
> > in that situation.
>
> Yes, we still do that in many (but not all) cases. I haven't removed any
> test surrounding a call to the sequencer (things like if (!nosequencer)
> {...} ).
Forgot to mention : I've committed a fix for --nosequencer.
--
Guillaume.
http://www.telegraph-road.org
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Rosegarden-devel mailing list
[EMAIL PROTECTED] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
