Re: [Flightgear-devel] upcoming release suggestion
Am 01.07.2012 05:52, schrieb syd adams: Before the next release , maybe it would be a good idea to disable those 'panel' outlines , which show up when you press 'C' to view hotspots. I don't think this was intentional. The outlines aren't even properly aligned on any aircraft I checked - so it just looks like a bug. And it's only visible on some aircraft. My guess is it only affects 2D elements - i.e. all the 2D map displays (radar/groundradar/maps) in glass cockpits. Also seems to be a relatively new issue - I hadn't even noticed before. Anyone knows when/how this started? Otherwise we'd need to check git commits. cheers, Thorsten -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.8.0: feature freeze starts now
Am 30.06.2012 15:02, schrieb Bertrand Coconnier: I don't know if it's only me, but all my efforts to match sg/fg/fgdata version were unsuccessful until I manually deleted src/Include/version.h in flightgear. After a complete rebuild and installation FlightGear was finally able to start but the above mentioned file was not restored ?!? version.h is generated whenever cmake runs. If you delete it, you need to call cmake again. It's also possible that a manual call to cmake is required after every version change, since we keep the version in a separate (non-cmake) file - which isn't really a standard solution. Either type your usual cmake command-line cmake , or enter your build directory and trigger a manual refresh/update of all makefiles using the most recent configuration with make rebuild_cache. cheers, Thorsten -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.8.0: feature freeze starts now
2012/7/1 ThorstenB bre...@gmail.com: Am 30.06.2012 15:02, schrieb Bertrand Coconnier: I don't know if it's only me, but all my efforts to match sg/fg/fgdata version were unsuccessful until I manually deleted src/Include/version.h in flightgear. After a complete rebuild and installation FlightGear was finally able to start but the above mentioned file was not restored ?!? version.h is generated whenever cmake runs. If you delete it, you need to call cmake again. It's also possible that a manual call to cmake is required after every version change, since we keep the version in a separate (non-cmake) file - which isn't really a standard solution. Either type your usual cmake command-line cmake , or enter your build directory and trigger a manual refresh/update of all makefiles using the most recent configuration with make rebuild_cache. cheers, Thorsten OK I finally understood what happened. Before 2.7.0, I was running 'cmake .' in flightgear root directory and it created all the object files amongst the source files. Since it is not the way to proceed with cmake, I decided to create a 'build' directory under flightgear and call 'cmake ..' in there instead. Unfortunately it seems I did not completely clean up the source directories since a copy of 'version.h' was still being in flightgear/src/Include. When the version moved to 2.8.0, 'cmake ..' created a correct version under flightgear/build/src/Include but the old version under flightgear/src/Include was no longer updated but was still used. Hence the issue. I looked for all the files named '*.in' and deleted the files that were created from them. Hopefully this should complete the clean up. Thanks Thorsten and sorry for the noise. Bertrand. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] upcoming release suggestion
On Sun, 2012-07-01 at 14:20 +0200, ThorstenB wrote: Am 01.07.2012 14:04, schrieb Gijs de Rooy: Before the next release , maybe it would be a good idea to disable those 'panel' outlines , which show up when you press 'C' to view hotspots. IIRC the bug is not in the displaying of the edges, but in the respective panel configs. The edges were introduced so developers can fix their aircraft. See http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg36695.html Good at least one of us reads/remembers devel posts ;-). But are we sure the panel outlines are accurate? They seem misplaced in every aircraft where they are visible (e.g. check 747 or 777). Possible that all aircraft are using incorrect panel coordinates. But it could also mean the panel outline isn't properly drawn - I see it's bottom left edge always aligned to the 2.5Ds panel's center. Is this working with any aircraft? And it's indeed a bit confusing to users. Maybe we should have a separate switch to enable displaying panel outlines... cheers, Thorsten I think users know that hotspots are yellow, the rectangles are cyan in colour, so that is an indicator to users that it isn't a normal hotspot, so they probably shouldn't get too confused. However I can't work out what the cyan rectangle is supposed to show, I've got some as well on the A380, and it's offset like everyone else says. S. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] upcoming release suggestion
On 1 Jul 2012, at 15:00, ThorstenB wrote: To be frank, I don't think that's the case. All new users don't know anything (yet). So, showing outlines which don't really mean anything to them, just adds to their confusion - whatever the colour (and every new user is already a bit confused when he looks at a cockpit for the first time). And the hotspot feature is especially meant for new users - experienced guys know where to click anyway. If we want panel outlines (to help aircraft designers) then it should be enabled through a different option. To be honest, when I added panel outlines (to help debug some hit-testing issues with panels), I always assumed this was a *developer* feature, not a 'novice user' feature. Hence not making it a separate switch. James -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.8.0: feature freeze starts now
On 1 Jul 2012, at 14:47, ThorstenB wrote: After 2.8, I'm going to add a cmake warning for builds inside the source tree. Some other projects even disallow such builds (throw a configuration error). Maybe we should do the same some day - and then get rid of the .gitignore magic. +1 to disallowing in-source builds here. Being able to just rm -rf the entire build directory (or dragdrop it into the trash :) ) to ensure a completely fresh build, without a need to clone the git repository from scratch, is just super-convenient. Indeed - as is having multiple build configurations in parallel - debug, release, shared, static... James -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.8.0: feature freeze starts now
On Sunday 01 July 2012 15:47:11 ThorstenB wrote: Yes, building inside the source tree has all kinds of pitfalls. And due to the .gitignore files which are there to ignore all generated files (and keep them from being accidentally committed to git), it's almost impossible to tell whether a source tree is still fresh clean or somehow tinted by a previous build. But there's still git clean -fdx which deletes all files and directories unknown to git ignoring the .gitignore file. In other words, it produces the same result as a completely fresh git clone. Another way to get the same result is to git clone from the local repository. The remote for tracking upstream can be added to the config later on. Stefan -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
