Most Kommander functions are supported; some (such as expr)
were obsoleted by new parser and are not available.
- debug(string, ...) - writes all parameters on stderr
- echo(string, ...) - writes all parameters on stdout
- dcop(string, ...) - calls DCOP function
- exec(string, shell) - executes external program
(using optional shell); returns output of that program
- i18n(string) - marks string for future translation
- env(string) - returns a value of environmental variable
- readSetting(key, default) - returns a value stored in config
file with given key; if there is no such value default is returned
- writeSetting(key, value) - writes pair
key and value in config file
New in Kommander 1.3
- return(value) - returns a value to the calling object (script, button...)
- createWidget(widget name, widget type, parent) - creates a new widget. You can then use mywidget.show(true) or place it in a table or toolbox. If you are putting an new widget on the form you need to consider layout issues. Kommander will not create layouts on the fly or edit pixel by pixel postioning (in most cases). This is confusing even in C++ development. We recommend you use a groupbox and do a layout in the dialog
for best control.
- connect(sender, signal, receiver, slot) - connect a widget signal to a widget slot. See the connection dialog and select similar widgets for possibilities. If for instance a signal looks like looks like execute(const QString&) that is exactly what must be in quotes there.
- disconnect(sender, signal, receiver, slot) - undo the connection as listed above. Again, exact syntax is essential.
- widgetExists(widget name) - remember you can use a variable name to reference a widget now. Us this when accessing created widgets to insure they are there. Calling a non-existant widget obviously will throw an error.
