From kde-devel Sat Oct 16 23:29:45 2004 From: LiuCougar Date: Sat, 16 Oct 2004 23:29:45 +0000 To: kde-devel Subject: Re: Execution replay for Qt/KDE applications Message-Id: <95580678041016162964aed6b () mail ! gmail ! com> X-MARC-Message: https://marc.info/?l=kde-devel&m=109796940711573 cool. I really interested in this kind of possibility. Maybe this can be merged into Qt in the future? What about setting up a project in the SF? Regards, On Sun, 17 Oct 2004 00:37:53 +0200, Oliver Oppitz wrote: > >> From: Benjamin Meyer > >> 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 << > -- "People's characters are strengthened through struggle against difficulties; they are weakened by comfort." - Old Chinese adage >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<