General and Desktop

Heh, i found. mlong was right :) this function was not mentioned in constructor :) Thanks!!!!

Would you wrap the code in @ (just before it and right after it), please :)

Congratulations! Good luck with the rest of your project.

[quote author="secretNinja" date="1303643751"]Pressing "Enter" two time do the work. Could two new lines be used instead of two lines of spaces in what you want to do?[/quote] I think it is different. I will try if I can implement this by using ManualWrap, Thanks everybody!

ok, Thanks :)

No need to reimplement QSystemTrayIconPrivate, just copy it's stuff to your own method and use a subclass or modified copy of QBalloonTip.

If you're printing a QTextDocument see http://developer.qt.nokia.com/faq/answer/is_it_possible_to_set_a_header_and_footer_when_printing_a_qtextdocument Otherwise, I'd be happy to see a QPrinter API that gives you a list of QPictures (=> what was printed) and lets the user modify them (by overpainting things etc.), then sends them to the actual printer.

I solved it by using a manual insert statement with placeholders, thank you for the "selection" hint :)

Thanks for the (tool)tip.

Looks like you are using COM, right? Why don't you use COM methods then? like CoCreateInstance etc?

I know in Microsoft visual studio you can add a shock wave flash player component to embed flash player into an application and then load a flash file and interact between the executable and .swf file. Yet, that is not a cross platform solution, but flash player is generally cross platform and what would give you the most control is embedding flash player into your application you could even modify values directly in the swf file (bit different for AS3). Also flash supports sockets so if you can't some how embed flash player into your application you can communicate with the flash content via sockets.

Add a container widget to the scroll area and set the minimum size to the container widget and place all the other widgets into the container widget you added. Then the scroll area should work.

Hello i heve solved using this: @LIBS += -L/home/luca/Scrivania/Luca/Pacchetti_C++/archive_1_0_6/lib -lbarchive INCLUDEPATH += /home/luca/Scrivania/Luca/Pacchetti_C++/archive_1_0_6/include@

AFAIR 3rd edition was used in QtScript.

The emit keyword itself doesn't do much. It is there for the looks of it. Essentially emitting a signal is calling a specific function. Signal/slot connections are by default made with the thread auto-detection enabled. The meta object will notice that different threads are being used and automatically a queued connection will be chosen. It is possible that a direct connection is enforced. In that case the called slot is executed in the emitting thread's context. I believe there is an article on the wiki explaining this more in detail. Bottom line is that signal/slot connections are locked, and therefore thread safe.

I do not know if this makes a difference or not(as it seems you are not using the signal/slot mechanism) but calling exec() within your run reimplementation allows the thread to run in its own event loop. This tends to prevent some memory allocation issues and allows for thread safe usage of signals and slots. Like i said I do not know if this will hold any relevance in your case.

Both interesting workarounds. The 'const' construct in all its flavors drives me crazy... Grumble. Anyway, the way I got around it was to define a couple of more signals and slots and connect them up to the created object, rather than rely on keeping a pointer around. That satisfies the issue of not accessing something if it's deleted (which was the intent of using QPointer in the first place), and 'connect' does not appear to violate the 'const' qualification. Thanks for the pointers (ar, ar). Keep them in mind for future necessities.

Another thing i want to mention: The data won't be displayed in the SqlTableView, unless I remove line 27, but at least it is displayed now. But I still have this problem with the duplicated columns. Any ideas?

I agree with Franzk: what would introducing this bring in terms of benefits that encapsulating a QGraphicsView does not?