Difference between revisions of "Integrating custom controls in Orbiter"
(→How to use ScreenGen to regenerate screens and how to use it) |
(→How to use ScreenGen to regenerate screens and how to use it) |
||
| Line 11: | Line 11: | ||
Let's say your screen has PK_Screen = 39, with the description "Computing": | Let's say your screen has PK_Screen = 39, with the description "Computing": | ||
| + | [[Image:Example.jpg]] | ||
[[A_record_from_Screen_table.PNG]] | [[A_record_from_Screen_table.PNG]] | ||
Revision as of 08:31, 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 possibility to do custom additional actions with that DesignObj.
Contents
How to associate a DesignObj to a screen
Once the parent design object is created with the Designer, go in pluto_main database and insert into Screen table a record with a description and few comments about the new screen. Then check Screen_DesignObj table and add a recording to link the screen with the designobj. You might also want to specify the UI and the Skin.
How to use ScreenGen to regenerate screens and how to use it
Run ScreenGen with -h <host> command line parameter and you should see in src/Gen_Devices/AllScreens.h that handlers for your need screens were added.
Let's say your screen has PK_Screen = 39, with the description "Computing":
A_record_from_Screen_table.PNG
In Screen_DesignObj,
