20,741
edits
Canvas widgets: Difference between revisions
Jump to navigation
Jump to search
m
→Nasal requirements
| Line 153: | Line 153: | ||
* Also I had to create a new event class (which uses most of the osgGA types) because the coordinates of the mouse where passed in the range [-1,1] which would make handling a bit more complicated... | * Also I had to create a new event class (which uses most of the osgGA types) because the coordinates of the mouse where passed in the range [-1,1] which would make handling a bit more complicated... | ||
=== Nasal requirements === | === Nasal requirements {{Feedback}} === | ||
The API needs to be extended to allow the creation of windows and placing canvases onto them. We also need a function which parses existing dialog xml files (reimplementing [http://gitorious.org/fg/flightgear/blobs/next/src/GUI/FGPUIDialog.cxx#line708 FGPUIDialog.cxx/FGPUIDialog::makeObject]) and maps them to the new canvas widgets. Each widgets sits in is own Nasal file (eg. inside $FG_DATA/gui/widgets) and has to be implemented using a hash with several required functions, implementing the abstract interface of a widget: | The API needs to be extended to allow the creation of windows and placing canvases onto them. We also need a function which parses existing dialog xml files (reimplementing [http://gitorious.org/fg/flightgear/blobs/next/src/GUI/FGPUIDialog.cxx#line708 FGPUIDialog.cxx/FGPUIDialog::makeObject]) and maps them to the new canvas widgets. Each widgets sits in is own Nasal file (eg. inside $FG_DATA/gui/widgets) and has to be implemented using a hash with several required functions, implementing the abstract interface of a widget: | ||