On 08/07/2014 06:16 PM, Tom Breton (Tehom) wrote: > * What you're proposing: Debug output for error situations to help users > troubleshoot, should they choose to. Turned on in the debug build.
RG_WARNING is a good name for this. After all, if it's an error, we should handle it better. > * What RG_DEBUG is doing now: Very detailed error messages intended for > maintainers. On short-term during intense development, per developer. Yeah. Easily turned off at the file and global level. I think RG_DEBUG/RG_NO_DEBUG_PRINT is fine as-is. > RG_ERROR seems promising. It looks easy enough to write. We'd want to > ensure that future developments understood which to use when. Comments and a wiki page should help. > An alias like RG_NOTIFY might be wanted for level-2 > messages that aren't warnings, such as "RG Translations loaded > successfully." or successfully loading the user's config file. RG_INFO is more in keeping with the standard nomenclature, I think. Definitely a good idea. Gives us an idea where we are stuck at startup. We would just need to keep it relatively quiet so it doesn't interfere with debugging. So, the proposal is for a new RG_WARNING and RG_INFO. I think they would both be helpful. Ted. ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
