Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Changes

Jump to: navigation, search

Release plan

653 bytes added, 18:45, 19 February 2013
m
2.10: a better about dialog
** a little irritation/frustration was caused due to the conflicting review statements concerning the new radio propagation code [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38905.html] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38825.html] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33692.html] - some of this boiled down to coding style related issues, highlighting the fact that different core developers have different "coding styles" and requirements when reviewing merge requests, because we still lack an official "FlightGear coding style guide" [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38958.html]
** merge requests that didn't make it into the previous release should probably be handled early during the upcoming release cycle
 
* '''Better bug reports and troubleshooting''':
** add a string property with list of startup arguments used by the user, for use in the about dialog
** add a property specifying if the binary is 32/64 bit for use in the about dialog
** add a property specifying the CMAKE_BUILD_TYPE variable used during compilation, for use in the about dialog (debug, release, RelWithDbgInfo)
** show the threading mode in use in the about dialog
** show average frame rate and frame spacing in about dialog
** add a property specifying how much physical RAM is detected
** is there a portable ARB/WGL extension to determine the amount of dedicated VRAM available ?
18,174
edits

Navigation menu