On Friday 13 June 2003 6:03 am, Levi Burton wrote: > SegmentMover* mover = > dynamic_cast<SegmentResizer*>(getToolBox()->getTool(SegmentMover::Too >lName)); > > It would actually segfault in the call to dynamic_cast. A mystery to > me, but not deleting the tool and just assigning the value 0 to it > seems to have fixed the problem, although there could be > ramifications i'm not aware of.
Uhm, a memory leak. Yes. > Also, the shift drag copy stuff doesnt seem to work now and I cannot > figure out why. I am sure it is something very simple. Um, again, doesn't seem to make me want to apply your patch. I understand why you're doing these changes but it sounds a bit broken. > I still think the move guides for multiple segments is weird. > Perhaps there should be fore, aft, top and bottom guides. Also -- > why are the guides QCanvasRectangles rather than QCanvasLines? Probably for a good reason but I can't remember why - oh yes, in Qt3.0 you can have QCanvasLines of greater than 1 pixel width and I wanted them wider. I also think guides for right and bottom is a fine idea but never got around to doing them. I see what you're getting at with the patch (and I agree that the crashing bugs are a pain on the segment canvas) but I don't want to apply it if it's going to break other stuff. I'll probably review it and apply it locally and see if I can fix it before committing anything. Don't know if I'll have time to do that today. R ------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
