Difference between revisions of "AVWizard specifications"
| Line 3: | Line 3: | ||
[[AVWizard script based user callable events]] | [[AVWizard script based user callable events]] | ||
| − | + | [[AVWizard's Control Events]] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | Events | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Note: any focus control is too a non-focus control, because it may be init, paint or closed, as any regular control | Note: any focus control is too a non-focus control, because it may be init, paint or closed, as any regular control | ||
Revision as of 08:33, 11 April 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. |
AVWizard script based user callable events
Note: any focus control is too a non-focus control, because it may be init, paint or closed, as any regular control
Controls: Page: parent control to all control, may be compared with a display Image: a picture area Label: control that describe a thing using some text ListBox (focus-able): a control that store multiple values Button (focus-able): a control that notify clicking Progress bar: a control that shows the progress of one action
Control definition:
object ControlName: <ControlType> [Propery = Value]
Event: [[[[action1;] action2; ] .... ;] action_n]
[object Child: <Control Type> <Child definitions>
End]
end
Properties and methods of controls:
- Page
- Image
- Label
- ListBox
ListBox properties ListBox events
- Button
Button properties Button events
- ProgressBar
ProgressBar properties ProgressBar events
Every screen will be stored in a file with SDF extension:
SDF = Screen Definition Page.
Every event called to a child control, will be called to the parent. Events will be parsed by control and if the event is not known, there should be no suitable code, else will call the default action.
Saving informations, set up the wizard defaults.
Every ListBox and Button will be saved to the next page in a list of stored options. Stored informations are next: Page/Control/Option
At $next event, every control will be saved, and at the $previous command every control with current page will be removed.
Command parsing
The command parsing is a stack, which calls a command and remove the command after.
The command: $generate_event push commands in pending state.
Exceptional cases: Following commands will destroy the stack: $next; $previous; CurrentControl.OnClose The next coomand destroy the screen, which clean up the all commands.
