Can QWidget::find find widgets from a different process?

4
votes

The documentation for QWidget::winId states (among other things) "If a widget is non-native (alien) and winId is invoked on it, that widget will be provided a native handle."

I'm not sure what 'alien' means in that context, but I'm choosing to ignore it for now. :)

So assuming that my widget now has a valid native handle associated with it, can I then pass that native handle to another process and into QWidget::find and get a valid QWidget object back within that second process?

I probably don't need to do too much else to the widget in the second process other than show/hide it and attach it to a parent widget. (It is guaranteed to not be attached to any parent widgets in the first process and never visible in the context of the first process).

If all the above works:

  1. How much control will the second process have over that widget?

  2. Will the first process receive user input events as if it were attached to the first process's UI, and will the first process be able to update the widget as normal?

James

1
qtqwidget
Are you wanting to get a QWidget from all applications including non-Qt applications? I don't know if this is possible on non-Qt applications. - Cameron Tinker
No, I have a very specific case where I have full control over both Qt applications in question. - user420442

1 Answers

2
votes

Let's take a look at Qt sources. 

QWidget *QWidget::find(WId id)
{
    return QWidgetPrivate::mapper ? QWidgetPrivate::mapper->value(id, 0) : 0;
}

find() can find a widget only if mapper contains it. The mapper is a static QHash<WId, QWidget *> variable. Items are inserted in this hash only in the QWidgetPrivate::setWinId method.

So, if a widget with a WId was created in another process, you can't find it using QWidget::find. This function doesn't use any native OS functions to find widgets.

Also see general description of alien widgets in Qt documentation:

Introduced in Qt 4.4, alien widgets are widgets unknown to the windowing system. They do not have a native window handle associated with them. This feature significantly speeds up widget painting, resizing, and removes flicker.