General and Desktop

Because I found the question intreaging, I took the liberty of "posting":http://ux.stackexchange.com/q/19312/13223 it on the User Experience stack exchange. I think the suggestion there is very interesting, but it will be quite hard to implement using Qt Widgets. Still, the idea is very neat. !http://i.stack.imgur.com/qIP3k.png(Suggested solution from UX StackExchange)!

I always call setrootindex when change path in the model but i dont know how to force update model

Hi Sajjad, I think I got it. The problem you have is, you need a mapping of the flat proxy items to the hierarchical tree items. This is what must be done in mapToSource/mapFromSource. If you know, you tree will not be deeper than 4 levels and no level will contain more then 255 elements, you could go something like: Each QModelIndex has a custom data (I think an int?) This could contain in each byte the index of the corresponding tree item in the level, like: Tree item: X3DNode --> 0x01FFFFFF (FF would mean not used!) Tree Item: BooleanFilter --> 0x0103FFFF (FF would mean not used!) Tree Item: PointNormalClipPane --> 0x010801FF (FF would mean not used!) If these restrictions do not work for you, you must find some other mapping that fits. mapToSouce is called with a QModelIndex of the proxy and must return a QModelIndex of the source model. You additionaly MUST handle the correct QModelIndex creation.

[quote author="Ashish Mittal" date="1332916135"]Thanks a lot leon!!!!!!!!!!!! You made my life really cool. I am being able to set the different proxy for different Qwebview inside a single application. your solution simply rockzz!!!!!!!! [/quote] You are welcome :) I am glad that the issue was solved but please note that I got the idea from a thread at "stackoverflow.com":http://stackoverflow.com/questions/6072574/how-do-i-manage-proxies-with-qt-qwebview.

Yeah I noticed that too. Don't know how to stop QtWebKit from doing so. You could try to use QDomDocument for parsing your HTML stuff again.

Have any solutions on this issue?

This has nothing to do with Qt Creator, which is just an IDE. Seems that you want to write a work processing application and want to create your own rich text format. Though QTextDocumentWriter support standard OpenDocument Format, you still can not read such format at present. Maybe you can join the KWord develop group if you like ;-)

This code works on the system having the "print problem"..so it appears it may be something associated with "rendering to a painter" code in the previous post...not the Mac Print drivers. @ QString detail; QTextStream out(&detail); // stream the report in HTML format // NOTE: html rules are ignored byt the setHtml function.. // specifically nested tables are not allowed // setting column sizes to a specific % not allowed out << "<table width="100%"><caption><b>" + QCoreApplication::applicationName() + "-" + QCoreApplication::applicationVersion() + "</b></caption>"; out << "<tr><td>User Record Summary for: " << ur->loadedname ; out << "</table><hr size=1>"; QPrinter *printer = new QPrinter(QPrinter::HighResolution); printer->setFullPage( true ); QPrintDialog *printDialog = new QPrintDialog( printer ); if (printDialog->exec() == QDialog::Accepted) { printer->setFullPage( true ); QTextDocument qtd; qtd.setHtml( detail ); qtd.print( printer ); } @ It doesn't make sense that the render to printer stuff works on most Macs, but one Mac has a problem. Argh!

You're probably looking for "restoreOverrideCursor":/doc/qt-4.8/qapplication.html#restoreOverrideCursor to undo the effects of setOverrideCursor.

lblText1 is binding to a function, the result of which cannot be known until the runtime starts processing proper. This happens much later, i.e. when the event loop is entered. lblText2 is binding to a constant expression. The QML runtime has no need to re-evaluate this at a later time since it is known to be constant. To make lblText2 behave like lblText1 you could bind the text property to a javascript function that just returns the string.

Thanks guys :D it worked. Btw I am making an openGL teaching tool and I am not a super creative person, would any of you be interested in testing my interface once I got it up and running? I would love to get some feedback to see if I am doing an ok job. Thanks for all of your help =]

"Seems that it is not supported at Qt 5":http://doc-snapshot.qt-project.org/5.0/xmlprocessing.html#xslt-2-0 too. You can search for an issue about import statement at "jira":https://bugreports.qt-project.org/.

This is my junk: {\rtf1\ansi\ansicpg1252\cocoartf1038\cocoasubrtf360 {\fonttbl\f0\fswiss\fcharset0 Helvetica;} {\colortbl;\red255\green255\blue255;} \vieww9000\viewh8400\viewkind0 \deftab720 \pard\pardeftab720\ql\qnatural \f0\fs24 \cf0 \ Hi! \ \ \ }

actually i'll more of like to know how to use them...

I am having this same problem using gSOAP to connect to a webservice. I am using Symbian S60 3rd Edition FP2 with Qt. The application runs fine, but after an hour or so gsoap stops being able to connect to the WS. If I restart the application it starts running fine. Any clue?

We do cross-platform, Windows, Linux and Linux embedded. You can continue developing using Visual Studio on Windows. What you have to worry about is: -) Only include headers that will be available on all platforms you want to deploy to. All standard C/C++ headers, as well as Qt are just fine. Anything Microsoft-specific cannot be used (or you have to take care of the platform-specific handling using #ifdef QT_OS_WIN and that like) -) You will have different compilers on different platforms. They can be closely related (e.g. MinGW on Windows versus GCC on Linux), or entirely different (e.g. VC compiler on Windows versus GCC on linux). This is not really an issue. The only thing is that different compilers tend to produce different warnings. That can be both a good and bad thing. -) The real issue is the build chain, and how your projects must be structured so they can be built on each platform. A possible solution (the one I use currently) is to use qmake project files (.pro). qmake can generate the necessary makefiles on all platforms where Qt is supported. -) When developing on Windows, never forget that Linux is case-sensitive with filenames. Things that compile on Windows will not compile on Linux, because on Linux @#include <Qstring.h>@ will not find the correct file. It must be either @#include <qstring.h>@ or @#include <QString>@ -) You will at least need to debug and test your applications on all platforms. Therefore, even if you keep Visual Studio as your main IDE, you'll need a debugger for each other target platform. Qt Creator is naturally a candidate here.

The setPlainText did the trick. Thank you! Best regards Richard

Thanks I now have creator working