General and Desktop

You're welcome. Good luck with your project!

way is not an options since is OS dependent. I'll try to put first options to practice. Thanks! Marked as solved. Regards, Jake

Download "Dependency Walker":http://www.dependencywalker.com Open your exe in it and see, what dlls you are missing If you use mingw, you also need mingw10.dll libstdgcc.dll from C:\QtSDK\mingw\bin (not sure about names, you better check yourself) Dependency walker is your best friend on Windows!

This is not Qt specific topic. This is called multisampling. It is a technique of anti-aliasing (getting rid of sharp, blocky edges). http://www.opengl.org/wiki/Multisampling This is an example how it looks ilke: http://doc.qt.digia.com/stable/opengl-samplebuffers.html To achieve this a special type of format is needed for front and back buffers (the ones you draw into). In vanilla OpenGL this is a platform specific feature. On windows you need to pass special attributes when creating OpenGL window (specifically WGL_SAMPLE_BUFFERS and WGL_SAMPLES). Qt handles it by calling setSampleBuffers(true) and setSamples(sampleCount) on QGLFormat before creating a GL widget. As for the quality - the more samples, the smoother the edges are. For now 2, 4 and in some cases 8 samples are supported I think, depending on your graphics hardware.

Thank you DerManu. It's a little confusing, but I'll try.

First Try searching in google about Qt3d.. You will get an idea about it. Then start working on your own, Even if you can't solve the problem, then just post your question here as a new thread, so that the Developer's can help you.... Thanks & Regards...

Try by including the Header file #include <QMouseEvent> Note: Always don't forget to use the necessary Headers. Including all the Header files is a good sign of programming practice... :) All d best..

You ended up in FakeVim mode where Creator behaves like an ancient text editor found on unix. To quit the FakeVim mode, unselect Tools > Options > FakeVim > Use FakeVim or press Alt+V,Alt+V. You can disable the fakevim plugin in Help > About Plugins to make sure you never end up in it again.

My guess is that they run a local proxy and use the local firewall to force traffic to go through that proxy. In my experience those products mostly provide a cozy feeling for the parents. Google usually has some easy to follow instructions to get around the restrictions, and if there is nothing there some kid in school will be able to help out.

I've done some research on this in January. First, QNetworkAccessManager is no solution, as it seems, as its a good HTTP source. But, you have to put the received content in a browser like enviroment, also parsing HTML is not really trivial, there is a tagsoup implementation which would do, but you got the problem, that some links are generated through javascript, so you really need to put that in a browser like thing -> QtWebKit. QtWebKit offers a lot of good stuff which you can use to crawl, f.e. it can extract all <a> tags (aka links). But, the problem here is, QtWebKit is not threadsafe, so you'd have to handle multiple Processes doing the work, in order to speed up the process.

Qt loads ssl libs dynamically(if not compiled with openssl-linked), so ssl libs should be in system library path or in the same folder to get loaded by Qt. And if this libs are not found, you don't even get SSLError fired, thats because your finished slot was fired just after calling post method of QNAM without any error and of cause without any reply...

Yeah, that's was my first thought. Set up a QStringList based on the search and then just create a few QTableViews through an iteration and insert them into a widget. Thanks!

Yes it does

circlebarplugin.h @#ifndef CIRCLEBARPLUGIN_H #define CIRCLEBARPLUGIN_H #include <QDesignerCustomWidgetInterface> class QExtensionManager; class CircleBarPlugin : public QObject, public QDesignerCustomWidgetInterface { Q_OBJECT Q_INTERFACES(QDesignerCustomWidgetInterface) public: CircleBarPlugin( QObject *parent = 0 ); bool isContainer() const; bool isInitialized() const; QIcon icon() const; QString codeTemplate() const; QString domXml() const; QString group() const; QString includeFile&#40;&#41; const; QString name() const; QString toolTip() const; QString whatsThis() const; QWidget *createWidget( QWidget *parent ); void initialize( QDesignerFormEditorInterface *core ); private: bool m_initialized; }; #endif /* CIRCLEBARPLUGIN_H */@ circlebarplugin.cpp @#include <QtPlugin> #include <QExtensionManager> #include <QDesignerFormEditorInterface> #include <QTimer> #include "circlebar.h" #include "circlebarplugin.h" CircleBarPlugin::CircleBarPlugin( QObject *parent ) { m_initialized = false; } bool CircleBarPlugin::isInitialized() const { return m_initialized; } void CircleBarPlugin::initialize( QDesignerFormEditorInterface *core ) { if( m_initialized ) return; m_initialized = true; } bool CircleBarPlugin::isContainer() const { return false; } QIcon CircleBarPlugin::icon() const { return QIcon(); } QString CircleBarPlugin::toolTip() const { return ""; } QString CircleBarPlugin::whatsThis() const { return ""; } QString CircleBarPlugin::codeTemplate() const { return ""; } QString CircleBarPlugin::includeFile() const { return "circlebar.h"; } QString CircleBarPlugin::name() const { return "CircleBar"; } QString CircleBarPlugin::domXml() const { return "<widget class="CircleBar" name="circleBar">\n" "</widget>\n"; } QString CircleBarPlugin::group() const { return "Book Widgets"; } QWidget *CircleBarPlugin::createWidget( QWidget *parent ) { return new CircleBar( parent ); } Q_EXPORT_PLUGIN2( circleBarPlugin, CircleBarPlugin )@

I don't know why didn't work that way, maybe somebody here could help providing an explication about this. I follow this approach (each class have it's own header and implementation file) for good programming habit, I do it without thinking. It's something that I've read in many C++ books. From my point of view a good source of information about this topic could be: "C++ Coding Standards":http://www.gotw.ca/publications/c++cs.htm and for a direct reading: "C++ Coding Standard":http://www.possibility.com/Cpp/CppCodingStandard.html#classes Glad to hear that you got it to work.

From QAbstractItemModel documentation: "The dataChanged() signal should be emitted if the data was successfully set. The base class implementation returns false. This function and data() must be reimplemented for editable models." Please check if dataChanged() signal is emitted. If not, you have to emit this signal