Mercurial > ldforge / changelog

now displays build type in the window title (unless a release build of a release), fixed some macro shenanigans

• Fri, 18 Oct 2013 22:30:08 +0300
• by Santeri Piippo <crimsondusk64@gmail.com> [Fri, 18 Oct 2013 22:30:08 +0300] rev 515
• now displays build type in the window title (unless a release build of a release), fixed some macro shenanigans

made messagelog handle messages with newlines

• Fri, 18 Oct 2013 22:07:26 +0300
• by Santeri Piippo <crimsondusk64@gmail.com> [Fri, 18 Oct 2013 22:07:26 +0300] rev 514
• made messagelog handle messages with newlines

Added a crash catcher which trigger under Linux. It calls GDB and tries to get a backtrace. Also integrated assertion failure handling to this new system. Removed the print() function in the process (because the new bomb box uses a text edit and QTextDocuments's print method clashes with the macro and I figured it was a good idea to rid it anyway) and replaced all calls with log().

• Fri, 18 Oct 2013 21:52:09 +0300
• by Santeri Piippo <crimsondusk64@gmail.com> [Fri, 18 Oct 2013 21:52:09 +0300] rev 513
• Added a crash catcher which trigger under Linux. It calls GDB and tries to get a backtrace. Also integrated assertion failure handling to this new system. Removed the print() function in the process (because the new bomb box uses a text edit and QTextDocuments's print method clashes with the macro and I figured it was a good idea to rid it anyway) and replaced all calls with log().

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.

- added debug/release build configuration. Debug builds are really useful things!

• Fri, 18 Oct 2013 17:47:05 +0300
• by Santeri Piippo <crimsondusk64@gmail.com> [Fri, 18 Oct 2013 17:47:05 +0300] rev 509
• - added debug/release build configuration. Debug builds are really useful things!
  - fixed an assertion failure with use of QString::operator[]