General and Desktop

[quote author="Denis Kormalev" date="1306693935"]Hm, strange bug with bolding all text. And nothing wrong in first post. Marius, do you see?[/quote] Strange indeed, thanks for reporting Denis.

Hi! You can find the key code so: @ void Widget::keyPressEvent(QKeyEvent *pe){ qDebug() << pe->key(); } @

OK, at least I know where I stand. Thank you all for your help, appreciated as always. -- William

That processImage method gets called from the right thread (in the example, the GUI thread, which is where the RenderThread object is living), so it's safe to use that way.

[quote author="Luca" date="1289835800"]Using QTcpSocket in a different thread require to pass the socket descriptor to the thread and construct the QTcpSocket in the QThread subclass as shown in the "threaded fortune server example":http://doc.qt.nokia.com/latest/network-threadedfortuneserver.html [/quote] BTW, I asked and I've been told that the docs (and the example) are wrong about that point: [quote]Note: The returned QTcpSocket object cannot be used from another thread. If you want to use an incoming connection from another thread, you need to override incomingConnection().[/quote]

[quote author="2beers" date="1306683337"]Hi everyone. Can I have multipart POST requests using QNetworkAccessManager ?? I read somewhere that this might be available only in qt 4.8? is that true? Thanks[/quote] Yes. 4.8 will introduce the QHttpMultiPart and the QHttpPart classes, which you can use to build mime/multipart HTTP requests. Overloads for QNetworkAccessManager::post and ::put (which take a QHttpMultiPart) will be introduced as well. In the meanwhile, you can do multipart requests, but you have handle everything by hand (or by using a 3rd party library).

Yes, that was exactly what I was looking for!! :D Thanks!! --

I can't find a solution to that problem. Nobody knows what can be done?

You can add that tag yourself. Simply edit your first message, and modify the subject line. I've done it for you this time, but next time, please do that yourself. Glad you got your issue solved!

@Denis Kormalev: Oh, run qmake again work. I'm deleting folder by hands, because think that if i recompile all it call qmake too. @kamilus just edit your post and add to begin [solved]

Sure, buddy :-)

I think it's time for bug report. I don't see why there is performance problems with scaling.

So, I think, It takes me a weeks to prepare it :D

As long as you do not save the image to its initial source file you may do several scalings. E.g. you start your application with different sizes of your graphic scene and you always read it from original file, you should not face problems. The quality of the displayed may change with the actual size, but a new start from original file will have different scaling and a different result. See also the input of Jota for scaling quality. Consequence, you should not destroy your original file. If you load your image once and you do several scalings with different sizes, you will certainly have deterioration of the image.

Nevermind, Administrator mode worked!

We provide PyQt bindings to Q7Goodies too. If you are developing a commercial application and don't mind buying a library then probably PyQ7Goodies is the easiest way to go.

it's work, once again thank You, You help me a lot [quote author="yshurik" date="1306611173"]Do you paint these frames in paintEvent? If not then there is no one who paint it. Is it painted by superclass QLabel? - then inside of your paintEvent() you need to call QLabel::paintEvent before your paintings (they will go to top).[/quote]