>> From: Benjamin Meyer <ben@meyerhome.net>
>> It would also be useful in developing tutorials for users. I.e. it  
>> would be
>> possible to let the application show which steps to take to  
>> activate/use a
>> certain feature.
>>  best,
>> Jeroen
>What about with dcop?
>http://developer.kde.org/documentation/tutorials/automation/

AFAIK dcop is an IPC mechanism and therefore only allows to call  
"functions" that are exported by the other application. In the document  
you pointed out there is a hint on automatically exporting all KActions or  
so. But even this is a different thing than recording all QEvents. QEvents  
are more low level (Keyboard, Mouse, Redraw etc.)

I wrote a very simple record/replay proof of concept program by now. It is  
limited to only record keystrokes at the moment, but I will extend it to  
all relevant events. When called with "-record" parameter the program  
opens a QTextEdit and records the keystrokes.  When called with "-replay"  
it opens a QTextEdit widget and replays those keys. Looks light a ghost  
typing ;-)

Regards, Oliver
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<