20,741
edits
Canvas news: Difference between revisions
Jump to navigation
Jump to search
m
→2017
(→2017) |
m (→2017) |
||
| Line 6: | Line 6: | ||
== 2017 == | == 2017 == | ||
=== Moving map/RNAV discussion === | |||
There's an interesting discussion that was started by David Megginson regarding implementing G1000-type systems on the mailing list: | |||
[https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/CAKor_TGugT%2Be%3DQhdNBqWq3Pn%2BCEq6iLZsgaB7HmiU%2BBoDK0vxQ%40mail.gmail.com/#msg35924395 https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/CAKor_TGugT%2Be%3DQhdNBqWq3Pn%2BCEq6iLZsgaB7HmiU%2BBoDK0vxQ%40mail.gmail.com/#msg35924395]<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=313697#p313697 | |||
|title = <nowiki> Re: zkv1000 reborn </nowiki> | |||
|author = <nowiki> stuart </nowiki> | |||
|date = Jul 4th, 2017 | |||
|added = Jul 4th, 2017 | |||
|script_version = 0.40 | |||
}}</ref> | |||
The airspace system is in the process of changing drastically<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35924395/ | |||
|title = <nowiki> [Flightgear-devel] RFD: FlightGear and the changing state of air | |||
navigation </nowiki> | |||
|author = <nowiki> David Megginson </nowiki> | |||
|date = Jul 3rd, 2017 | |||
|added = Jul 3rd, 2017 | |||
|script_version = 0.40 | |||
}}</ref> | |||
zakh on the forum has been developing a Garmin G1000 clone called thekv1000: https://forum.flightgear.org/viewtopic.php?f=14&t=32056 <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35925226/ | |||
|title = <nowiki> Re: [Flightgear-devel] RFD: FlightGear and the changing state of | |||
air navigation </nowiki> | |||
|author = <nowiki> Stuart Buchanan </nowiki> | |||
|date = Jul 3rd, 2017 | |||
|added = Jul 3rd, 2017 | |||
|script_version = 0.40 | |||
}}</ref> | |||
the G1000 has multiple pages of data with data entry for flightplans etc. Stuart is sure there is a lot that has been learned by the Shuttle team that can be passed on as "best practise". The Route Manager should be able to handle most of the "magenta line" tasks, but it may be that the more complicated routing such as the RF approach, fly-by vs fly-over requires some new autopilot coding as you describe.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35925369/ | |||
|title = <nowiki> Re: [Flightgear-devel] RFD: FlightGear and the changing state of | |||
air navigation </nowiki> | |||
|author = <nowiki> Stuart Buchanan </nowiki> | |||
|date = Jul 3rd, 2017 | |||
|added = Jul 3rd, 2017 | |||
|script_version = 0.40 | |||
}}</ref> | |||
Stuart is hoping to to optimize the property access and become more familiar with the Canvas C++ code so that he can help bridge the cap between core and Canvas client developers. He thinks James has some thoughts on the Canvas C++, so he'll want to coordinate with him as well.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=313787#p313787 | |||
|title = <nowiki> Re: zkv1000 reborn </nowiki> | |||
|author = <nowiki> stuart </nowiki> | |||
|date = Jul 6th, 2017 | |||
|added = Jul 6th, 2017 | |||
|script_version = 0.40 | |||
}}</ref> | |||
=== Groups and Colors === | === Groups and Colors === | ||
Thorsten learned something rather important about canvas: After doing canvas a while, most of us love the concept to suitably group things and then translate or hide the whole group, which is a very performance-friendly way to get the job done compared with moving all elements. | Thorsten learned something rather important about canvas: After doing canvas a while, most of us love the concept to suitably group things and then translate or hide the whole group, which is a very performance-friendly way to get the job done compared with moving all elements. | ||