Hello Sebastian,
Actions are always triggered from within the GUI. There are however some
workarounds, they all involve creating a an action with a custom 'render' method
that returns a custom widget :
1. the widget could have a timer defined that triggers the gui_run of the action
every now and then. the action then checks if there is a pending xmlrpc request,
end handles it.
2. the widget could have a slot to trigger the gui_run of the action. the thread running
the xmlrpc server could then emit a signal that is connected throught the slot.
Qt signal-slots work cross-threads. So the xmlrpc server could run in its own thread,
keeping it always responsive.
Cheers,
Erik