Difference between revisions of "Integrating custom controls in Orbiter"
From LinuxMCE
| Line 1: | Line 1: | ||
| − | <table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>== | + | <table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>== 1. The concept of screen in Orbiter == |
| + | A ''DesignObj'' is a graphic object from Orbiter. Each ''DesignObj'' may be a collection of ''DesignObj'' children and so on. On parent ''DesignObj'' can be associated with a screen, which gives the programmer the | ||
| − | + | 1.1 | |
| − | + | ||
| − | + | == 2. ScreenHandler and how to register a callback == | |
| + | |||
| + | |||
| + | == 3. How to send task to task manager. == | ||
Revision as of 08:02, 2 May 2006
| This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto. |
A DesignObj is a graphic object from Orbiter. Each DesignObj may be a collection of DesignObj children and so on. On parent DesignObj can be associated with a screen, which gives the programmer the
1.1
