Bring window to front -> raise(),show(),activateWindow() don't work on Windows

andre

I would re-think the design criteria. There is a reason window managers don't allow windows of not-active applications to put themselves at the foreground. Why try to circumvent that? What makes your application so super-extra-special that it would need to go around these intentional limitations?

Hedge

@Volker:
I still work on z/OS and like my applications slim, so having a QtWebkit just for that purpose isn't an option.

@Ander:
My application isn't super special but it brings the browser in front of itself as well. It would be ok if it was possible to start the browser behind it (my application is only like 300 x 400 pixels, not resizeable).

An option would be to keep it topmost until the user either allows access to Twitter via oAuth v1 or the request times out but I don't really want to play with the topmost-property as that is what I consider a design-fault.

goetz

Maybe "QTextBrowser":http://doc.qt.nokia.com/4.7/qtextbrowser.html fits your needs already. It does not need webkit and is included in QtGui module, that you need anyways.

Hedge

Good idea, but the user needs to click on a button (image) on the webpage that opens to authorize my application to aborminate his Twitter-account.

goetz

The text browser class does not handle network access by default, so you would have to add this yourself. I don't know if that's worth the effort. I personally would just include webkit and don't care for the size of the application (bandwidth is barely a problem nowadays...)

situ117

To start the browser in background why don't you try something like this ?

@
QLabel* label = new QLabel("Hi");
label->show();

QProcess* p = new QProcess();
QObject::connect(p,SIGNAL(started()),label,SLOT(raise()));
p->start("firefox");
@

So as soon as the browser starts your application will be brought to front.

EDIT: Replace raise() with your customized function which you're using to bring window to top.

Hedge

@situ117:

I don't know how that works with the users default browser.

@Volker:

The tool is 1.2 MB right now (.NET, I know that doesn't cut) and was 1.8MB when I coded it first in Object Pascal (yeah I really wrote it three times).

The Qt-Version on Windows is 7.5MB due to my custom dll's. The users are likely to ask how I justify that increased size. I really want it to be as small as possible.

goetz

I'd say having it cross platform does count :-)

redstoneleo

A valid solution here https://stackoverflow.com/a/10808934/1485853