General and Desktop

also tested it on windows now, no problems there. 1 font f.e is STIXGeneral. can i filter them out somehow?

Did you have already a look onto "Printing with Qt":http://developer.qt.nokia.com/doc/qt-4.8/printing.html ?

Oh, after removing 35~36 lines of above, it looks like working just the way what i want. But, I'm still afraid this kind of implementation is another make my hand dirty kinda thing. Is there another kinda 'official' way to get this value out of it?

You can call terminate() to all your threads before you exit your program, by reimplementing close event on your main window and insert there a call to terminate all threads.

even i tried using QFileSystem...but getting runtime error... Plz look at this post---->http://developer.qt.nokia.com/forums/viewthread/14343/

Hi Kromacast, Here is the link sourceware.org/gdb/onlinedocs/gdb.pdf.gz Cheers Aquib

[quote author="Lukas Geyer" date="1328775254"] Does classifying the same image in the same thread twice result in the same output?[/quote] Yes. Executing run twice sequentially creates identical results and executing start twice sequentially creates identical results.

First of all, it's not a really good idea to use CP1251 to insert some cyrillic strings to your code. It's much better to use UTF8 everywhere (esp. if you want your application to be able to compile and work on the other platforms :) I guess you are compiling your application for Windows? Is there any other places in your code where the codecs may be changed? Maybe you need to try to build debug version of Qt from sources, toggle a breakpoint somewhere inside the QTextCodec::setCodecForCStrings and QTextCodec::setCodecForTr functions and take a look if there is any other code in your project toggling this functions. Here is a fragment of code used by our current project and it works like a charm: @void setupLocale() { // Установка локали по умолчанию QLocale russianLocale(QLocale::Russian, QLocale::RussianFederation); QLocale::setDefault(russianLocale); // Установка текстовых кодеков QTextCodec* defaultCodec = QTextCodec::codecForName("UTF-8"); QTextCodec::setCodecForTr(defaultCodec); QTextCodec::setCodecForLocale(defaultCodec); QTextCodec::setCodecForCStrings(defaultCodec); // Устанока QTranslator для Qt на текущую локаль QTranslator* qtTranslator = new QTranslator(QCoreApplication::instance()); qtTranslator->load("qt_ru_RU", QLibraryInfo::location(QLibraryInfo::TranslationsPath)); QCoreApplication::instance()->installTranslator(qtTranslator); } @ (I'm sorry for the comments written in russian, but your profile shows me that it will be no problem for you to understand it ;)

Good guess. When I query in.atEnd(), it is false.

Volker, you are a mad scientist ;-) I'll give that a try in the next couple of days.

you guessed, but analyzing chrome http request with wireshark i didn't notice nothing unusual...my application receive 403 error immediatly after 'get' request...i thought it was a user-agent problem, but i have copied chrome ones... anyway QNAM maintains cookies automatically and represents it when asked by the server, doesn't it?

[quote author="DominicanTech" date="1328505857"]When I create the UI using form, Qt automatically creates the .ui qml for me[/quote] You are confusing interface paradigms here. The things you create based on widgets will not result in QML at all. That will result in a c++ header file (after processing by the uic tools wich will be run by qmake), which is then included in your application.

[quote author="n00b123" date="1328626354"]Hello Volker no i did not use the macdeployqt tool. I don't saw it in the how to: http://developer.qt.nokia.com/doc/qt-4.8/deployment-mac.html[/quote] Well, searching for it on that page points me right to it...

"Here":http://www.google.com/imgres?um=1&hl=en&client=ubuntu&sa=N&channel=fs&gl=uk&biw=1553&bih=798&tbm=isch&tbnid=TU8tJeieQP3JCM:&imgrefurl=http://msdn.microsoft.com/en-us/library/ms996437.aspx&docid=FGb115q9lXjvdM&imgurl=http://i.msdn.microsoft.com/dynimg/IC77718.gif&w=282&h=350&ei=qN0zT4vLDIal0QWqup2-Ag&zoom=1&iact=rc&dur=347&sig=113596841083879039400&page=2&tbnh=134&tbnw=108&start=32&ndsp=39&ved=1t:429,r:12,s:32&tx=64&ty=88 is an image of a tree view, with a wide entry that has necessitated a scroll bar. I would like my tree view to look like this, except I would like the blue selection background the 'Ringer' entry to always fill the whole width of the white area - the way items are highlighted in "this image.":http://www.google.com/imgres?um=1&hl=en&client=ubuntu&hs=zWW&sa=N&channel=fs&gl=uk&biw=1600&bih=827&tbm=isch&tbnid=Q8VVttKbSOONCM:&imgrefurl=http://www.palminfocenter.com/news/7805/splashid-4-for-mac-os-x-released/&docid=noft9BWfGJd_eM&imgurl=http://www.palminfocenter.com/images/splashid-mac-desktop-v4.jpg&w=550&h=310&ei=vd4zT9iGM8rK0QXysI3DAg&zoom=1&iact=rc&dur=431&sig=113596841083879039400&page=1&tbnh=107&tbnw=189&start=0&ndsp=28&ved=1t:429,r:2,s:0&tx=119&ty=72 I would also like the scroll bar to be visible only when there are overly wide items visible in the tree. I hope that has helped to clarify a bit.

Hi, If I understand you right, you want to composite images. You can use "QPainter::setCompositionMode":http://developer.qt.nokia.com/doc/qt-4.8/qpainter.html#setCompositionMode

Ok so this code works well on device : .pro @mydeployment.sources = myfolder/* mydeployment.path = mydeploymentfolder DEPLOYMENT += mydeployment@ .cpp @ QDir d(QApplication::applicationDirPath() + "/mydeploymentfolder"); qDebug() << d.exists() << d.entryList(); @ However, this is not working on Nokia SDK Simulator. Any idea to make it work on Nokia SDK Simulator ?

I would not say it is a general preference, but in this specific case I would prefer a simple regular expression over QDomDocument, because it is just a waste of resources. QXmlStreamReader might be a viable option, but it still requires me to write a multitude of code just to remove some character padding around a string and an integer value (and I can hardly think of anything more extendable then a nongreedy regular expression match combined with <code>*.**</code>). Yes, regular expressions should not be used as a replacement for XML parsing in general, when it comes to different encodings, a varying document structure, schema validation, optional elements and attributes and all the other gruesomeness of XML, but in this specific case ("... if it is just the two fields ..."), where two basic datatypes are paddad by some well-defined and static characters, a simple regular expression is a readable (subjective, I agree on that to a certain degree), extension-resistant single-line construct. This conclusion will change if the conditions change.

No necroposting, please. There's no need to wake the dead - the thread had its last response for more than one year ago and it was resolved already. Thanks.