Mercurial > ldforge / changelog

fixed: LDForge would crash if message log got full - the older lines would be removed with ::erase, which now expects an iterator because of the recent transition to QList. Why does QList::iterator allow 0 to be passed?

• Fri, 18 Oct 2013 18:16:54 +0300
• by Santeri Piippo <crimsondusk64@gmail.com> [Fri, 18 Oct 2013 18:16:54 +0300] rev 512
• fixed: LDForge would crash if message log got full - the older lines would be removed with ::erase, which now expects an iterator because of the recent transition to QList. Why does QList::iterator allow 0 to be passed?

fixed a small memory leak

• Fri, 18 Oct 2013 18:12:23 +0300
• by Santeri Piippo <crimsondusk64@gmail.com> [Fri, 18 Oct 2013 18:12:23 +0300] rev 511
• fixed a small memory leak

Fixed: LDForge would sometimes crash over unitialized data in the GL renderer. This crash sure eluded me for a while. Turned out zoomToFit(), which uses m_width and m_height is called before resizeGL() which initializes these variables. This data is used in an operator new[] call.

• Fri, 18 Oct 2013 17:57:42 +0300
• by Santeri Piippo <crimsondusk64@gmail.com> [Fri, 18 Oct 2013 17:57:42 +0300] rev 510
• Fixed: LDForge would sometimes crash over unitialized data in the GL renderer. This crash sure eluded me for a while. Turned out zoomToFit(), which uses m_width and m_height is called before resizeGL() which initializes these variables. This data is used in an operator new[] call.