Originally created by: gijsrooy
Originally owned by: zakalawe@mac.com
*What steps will reproduce the problem?*
1. Launch FlightGear (duh).
2. Open the route-manager dialog, to initialize the property tree.
3. Cloe the dialog.
4. Set /autopilot/route-manager/departure/runway to a runwaynumber of the airport you're at.
5. Open the dialog again.
*What is the expected output? What do you see instead?*
The dialog should now display the runway number as set in the property tree. Same behaviour is observed when you select a runway through the dialog and close/open the dialog afterwards. Again, the original runway is selected, rather than the user-set one.
It works fine for airports and also for destination runways (altough for the later, setting the property tree value does not update the dialog; while it does do that for airports).
*What version (or GIT date / Hudson build number)?*
Current Git, Hudson #166 from Win32-installer.
*What operating system and graphics card?*
Windows Vista
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
Problem here is FGRouteMgr::initAtPosition, which should respect existing values for departure airport/runway. Will fix this 'soon', and probably merge to 2.2.0
Labels: -Nasal fixable
Status: Accepted
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
(No comment was entered for this change.)
Owner: zakalawe
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
(No comment was entered for this change.)
Cc: -zakalawe gijsrooy
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
Fixed by:
http://gitorious.org/fg/flightgear/commit/54ef43878f50eb99d3773ceef099383886d95bf1
Note there looks to be a separate, Nasal issue with setting the runway before the dialog opens, so leaving this open for Gijs to test and comment, since further work may be required.
Status: Testing
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Gijs (see last comment): successfully tested or more comments? otherwise considered fixed.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gijsrooy
Works, thanks Thorsten!
Status: Verified
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Temp
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Verified