KDE-Forum.org

I am a newbie in Qt programming (and also in C++).
I have read several books & manuals but I lack experience.
In order to learn Qt I have to build up a project (the best way to learn): at the moment I am interested in interprocess communication.
I use Linux Mandrake and KDE. Due to the fact that KDE has been written in Qt, and has embedded a tool like DCOP (Desktop Communication Protocol), is it possible to make a Qt sw that send simulated keystrokes (or even simulated mouse moves/clicks) to Konqueror browser to operate it?

Thank you for your replay, but it's not very useful.
I explain why (at least for me...):
You say:

Quoted

DCOP is not used to send key strikes, for that, the X11 event queues are
used and they can be used fromQt. DCOP can, however, be used to control
Konqueror.

I did not say that "DCOP is used to send keystrokes" but I asked for any information (mainly in the form of web references) on:

Quoted

Qt sw that send simulated keystrokes
(or even simulated mouse moves/clicks) to Konqueror browser

My Reference to DCOP was merely to remind that a lightweight mechanism for inter-process communication already exists and it is used by KDE.Correctly you said that in your opinion the kestroke's simulation can be achieved by "X11 event queues", but for me (beeing a newbie) that is too generic.
Googling around I did not find much on the subject, expecially considering the fact that the event (the keystroke) must be sent to a process not created by me (I'm not a Konqueror's programmer!).
Your last assertion on "DCOP used to control Konqueror" is very interesting, but we must agree on what "control" means.
I know that using dcop from consolle, you can start Konqueror with a given URL and perhaps even open from it a new window of Kmail with the "To" field filled with a string of your choice, but I want to completely control Konqueror from sw simulating my keystrokes and/or mouse operations.
This is similar to what that can be achieved in Windows by macro languages like AutoIt or Macro Express or even by macro registration in Office.

I am surprised that Linux in this field is not up to date...

Hi,
thanks again to e8johan and wysota.
Two days ago I found "The Indipendent Qt Tutorial" by e8johan; I am studying it together with the Trolltech's Tutorials. Thanks also for that!
Of the two web reference given by e8johan, the second was already known, but the first one seems interesting.
As far as my incorrect use of the term "inter-process communication", call it as you like, but the result does not change (I have not seen any example of keyboard/mouse emulation to control from sw another application!).

http://www.x.org/X11_clientdesign.html
does not work!

...for me, no! And unluckily I havent found no web mirroring for the html file.

It does not work either, but thanks all the same!

I am grateful for your interest... but it is not so important.
Anyway I am contacting a guy that claims to controll an application by means of keypresses sent to the window .

Thank you for your replay and for the web reference. Unfortunately the target is a little different :

Quoted

x2x allows the keyboard and mouse on one ("from") X display to control another ("to") X display.

I don't want to control another display, unless another X application can be considered "another X display".
I hoped to have found the solution with a guy who pretended to control another application by means of simulated keypresses but also in this case it was only a method to implement shortcuts.
By sending keystrokes to a window I do not intend to launch a shortcut for a given action, but merely simulating what I do by hand.

I tought that was easy like under Windows with the macro languages like AutoIt, Macro Express, Macro Scheduler or even the macro registration in Office).

But I mailed one of the programmers of KDE and DCOP and he said that this was not so easy.

I refer his exact words:

Quoted

"Well, it would be in principle possible, if someone would add DCOP wrappers around a general event handler.
But I doubt such a mechanism already exists.
Konqueror's (or any KDE app's) ensemble of keyboard strokes and mouse events is in fact the result of the reunion of a large number of such notions that
are configured and provided at multiple levels in the KDE framework.
Some of these events are configured at Qt level (e.g. the TAB keystroke that moves the cursor from widget to widget).
Others are offered by the KDE libs (e.g. the Ctrl+C that allows copying). Others by the application itself (e.g. Ctrl+Home for going to the home page in konqueror).
Thus, making a wrapper around all this multitude is probably a very involved task."

So I gave up, expecting that someone else solved the problem, beeing all that too far from my knowledges.
And, in effect, I know that there is a working group, to add automation tools to linux but it is in a too early stage.