General and Desktop

That is going to be a problem then: your GUI thread is obviously very bussy with the webview and the embedded video. There is not much you can do about that. Sorry.

Thanks for the link: I hadn't seen it on my search. I added a line to each .pro file in the subdirs template project. Thanks!

Thanks mlong, thanks again Andre... I reading some online documentation and some free books of c++, but I could not understand how to create a class using a getter and setter referenced (it's right?). Off course I really think that it's a good idea, but like always my term in sort to show something to my client, and I'm studying and Working at same time... Thanks!

Have a look at [[doc:QGlWidget]] and [[doc:QGraphicsView]]

Sounds like a good suggestion. You might: create a bugreport with your suggestion Better yet, a patch for now, create a doc note on this.

[quote author="AndreAhmed" date="1341314891"]Is there any idea guys ?[/quote] Don't "kick" your topics, especially this fast. Allow at least two days, but idealy up to a week for people to answer.

Nope. In QML, this would be trivial, but in the widget world these kinds of scenario's were not taken into account.

ok tnx alot

Tell us when the preferred PIPE, SHARED MEMORY, and when the LOAD DATA INFILE. Maybe there are those who have tried all the options

[quote author="AndreAhmed" date="1341306224"]I have posted another topic, would love to see your reply.[/quote] Just now I am busy, but in 20 minutes I will free and will try to answer;)

[quote author="dcbasso" date="1341259385"]Sorry, my layout was missing the layout component to handle with added widget![/quote] So... it is solved?

FYI: I finally was able to display U+FFFF code points by explicitly setting the QLabel, QTextEdit, or QLineEdit style sheets as follows: @ font-family: "Segoe UI","Cambria Math";@ where Cambria Math is a font that contains the U+FFFF code points on my system. For some reason the font matching algorithm doesn't find Cambria Math on my system unless the font-family explicitly includes a font with code points above U+FFFF. With the above font-family declaration my text is rendered as Sagoe UI except for the U+FFFF code points which is rendered as Cambria Math. Note: I tried setting various combinations of font families and styles but the above was the only method that worked. Even setting the font-family or directly setting the font to Cambria failed to find the U+FFFF code points. I also checked on the lastResortFont(). It always came out as arial no matter how the font or font-family is set. I had hoped that I could set the last resort font to Cambria Math so I wouldn't have to worry about setting the stylesheet but I don't know where this parameter is set.

Thank you for the suggestions. Since this will be my first project that actually uses Qt for more than an IDE, I'd like a recommendation on an example as well, something I can use as a starting point. Any ideas?

I'm not Robert :) anyway: in WM_POWERBROADCAST test for DBT_DEVICEARRIVAL if it is, the lParam will be then DEV_BROADCAST_HDR structure. Check for dbch_devicetype in this structure and if it equals to DBT_DEVTYP_OEM your lParam is the DEV_BROADCAST_OEM structure, just cast lParam to DEV_BROADCAST_OEM. also read about SetupDiGetDeviceInterfaceDetail WINAPI function. bq. Second even if I get this object or pointer, how do i get the OS name ?? if OEM is "Apple iPhone bla bla", you have got iPhone, do more specific tasks with iPhone SDK to get OS version or whatever you need... If it is HTC, do the over stuff... and so on... You need to search on Specific Device devoplers forum for more information on how to get OS information for specified device. Qt and WINAPI can't help you here(WINAPI can help only for WM devices, maybe for WP too)

Just a quick bump. Does anyone have any idea what it is I'm doing wrong?

[solved]

moderators note: @ehulser: I have merged your three consecutive postings into a single one. If you want to add to a previous posting, especially if there have been no other replies in the mean time, please edit your previous post instead of creating a new one. Also, please use @ tags to surround code sections, so they can be properly formatted.