> If I were you, I would do a clean build WITHOUT debugging this time. In > a production build, this should not happen. The other choice is to find > and comment out a line of Rosegarden code, to make it stop crashing on > Qt warnings.
Come to think of it, this is a good experiment. I fear that if you do a production build, you will still see a crash here on that useless noisy warning. We tried to fix that problem, and the result you get will be informative as to whether or not the fix worked. If you still get a crash after doing a production build, or if you want to run a debug build to help with other bug reporting (not a bad idea!) I will dig into the code one day soon and tell you what small change to make to get this problem to go away. You just have to stick a // in front of one line, but I forget where that line is, and have no time to look at the moment. -- D. Michael McIntyre ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Rosegarden-user mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
