On 04/25/2015 03:28 PM, Ted Felix wrote:

>     r13912 was preventing the effects of zooming all the way out to 2.5%
> which is why it appeared to fix the crash.

Thanks for finding the problem with that, Ted.  I kind of figured it was 
one of those too easy band aid patches chasing symptoms instead of 
causes, but I didn't discover the expected side effects, so I figured 
we'd see how it went.

>     The crash happens along with many of these in the debug output:
>
> RosegardenScrollView::updateBottomWidgetGeometry
>
>     So that's a clue anyway.  Might be some sort of endless loop.

That threw up a red flag in my memory banks.  I think that's one of 
those things that got mangled beyond recognition in the port, and never 
sorted out.  There were contentsMoving(int,int) signals all over the 
thing I'm remembering (which may not have been this after all), and I 
never found anything to replace them, or worked out what they were 
supposed to have been for, and I left it all dangling.

No time to investigate.
-- 
D. Michael McIntyre

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

Reply via email to