On Tuesday 05 August 2003 16:37, Chris Cannam wrote:
>
> without bothering to catch the exception that sequencerCall might
> throw, is asking for trouble.
Yes, but we should catch the exception at a higher level. There's little point
in having exceptions if we catch them at the lowest possible level, might as
well keep the original bool return codes then.
> For a start it currently prevents
> the app from running at all when --nosequencer is given.
Yes, the sequencerCall() and sequencerSend() methods should be no-ops if
--nosequencer is given.
> I'm not sure how many occurrences of this there are, but they need to
> be fixed.
Will do right away.
--
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
