On Tuesday 17 June 2003 05:17 pm, Chris Cannam wrote: > I get a lot of runtime problems with Qt from misdescribing slots in > connect() arguments and the like, but they don't usually cause crashes. > > Can you give an example of something that's hit you with a crash > recently when you thought it should have warned you at compile time?
This isn't as bad as it was looking at first, though I discovered a fun way to crash. If you try to connect something before creating the object... connect(blah,blah) foo = new blah; then it bombs. I pasted my code in the wrong spot. Looked right at it a dozen times without realizing that too. Duh. I think the other problems that slipped by, like ignoring valuechanged for valueChanged and whatnot would have just resulted in widgets that didn't work properly. Annoying, but not fatal as you say. -- Michael McIntyre USDA zone 6b in SW VA, USA Silvan <[EMAIL PROTECTED]> Linux Druid ----------[ registered Linux user #243621 ]--------- http://www.geocities.com/Paris/Rue/5407/index.html ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
