Qt Creator and other tools

I would recommend trying another channel than (just) this forum then though. Perhaps ask on IRC at #qt or even #qt-labs, if #qt doesn't yield anything. I don't see that many Trolls frequenting this forum (though there are some, of course).

reactive: A "bug report":http://bugreports.qt.nokia.com/ with some attached project showing the behavior would be really nice.

http://bugreports.qt.nokia.com/browse/QTCREATORBUG-4008

Does anyone know of any example that make good and appropriate use of the .ui file along with several separate class files.

[quote author="kernelpanicker" date="1299273375"] but I did see it in the Add/Remove Software gui tool in Gnome. [/quote] i had a problem with the distrubeted version of ubuntu, so i had to use the original package from Qt. [quote]Now the issue is to get the version I installed out of the system so I can install it with the gui tool, which will then track updates for me automatically, as well as track what goes in so I can remove it.[/quote] i already told you how to remove. its not difficult.[/quote] [quote] I'll check what you mentioned but I'm still nervous it put itself in various places in the system... after all, it appears in the menus in Gnome...[/quote] When you use linux, the sooner or later you have to change something that is not suported from your distribution. Never be afraid to change something. you can always change it back. check the lfs-book and try to setup one of your own. it takes for the first time, only 1 or 2 days. but you have learned almost everything you need from your system in that time. if you still dont want to remove it, you also could install the other version next to it, it doesnt really matter.

libpng is linked statically. What I wanted to say is: if I call for example "png_create_read_struct" function which resides in libpng library, debug my application, step into "png_create_read_struct" function, I expect debugger to go in "pngpread.c" file from my libpng, but the debugger shows, is "pngread.c" from qt/src/3rdparty/libpng. From what I understand, by default, Qt supports png read/write linked in QtGui, so this is my puzzle.

The DevNet status has nothing to do with the bug tracker. The logins are completely independent.

Is there any way to change OUT_PWD via cmd? (It seems like I am asking myself, sorry guys...) I've tried this: @qmake.exe -makefile make\Makefile@

Hello. I have installed release 2.1 version on MacOSX 10.6.6 with latest updates. If i enable "FakeVIM", the basic forward and backward movement (Ctrl-F and Ctrl-B) are not working :(. Is it intended, or i need to do some additional configuration? This seems to be a MacOS specific problem since Ctrl-F and Ctrl-B works fine with 2.1 version on Windows 7.

Oooooh, before trying to build/generate the qvfb tool by myself, I forgot to choose the Qt lib I just built... So I entered again in the Qt Creator to update the qvfb ".pro" project by setting reference to the correct Qt lib (the one I built by myself), changing the default reference value "QT in path" by the "4.7.1" one, which, I guess, was the one corresponding to what I just built before... Then trying to rebuild qvfb goes farther but stops again with a new compiling error (argggh... !?), complaining about one more missing "X11/extensions/XTest.h" include file... Well I looked around the web with Google and I found that "XTest.h" was belonging to "libxtst" which I guess was not installed by default on my Fedora 14 system... So I did a "yum search libxtst" to look for exact package/component name for "libxtst" on my Fedora 14 system, and then, I decided to install libXtst.x86_64 : X.Org X11 libXtst runtime library and libXtst-devel.x86_64 : X.Org X11 libXtst development package: as root: yum install libXtst.x86_64 libXtst-devel.x86_64 As a result, I succesfully regenerated the binary executable file for qvfb tool... Great ! :-) Alain-Pierre

The actual definition of Q_EXPORT_PLUGIN2 depends on the value of QT_STATICPLUGIN. One of these uses the value of PLUGIN.

you should've looked at how the Qt sources are organized to find it out by yourself :) Tobias is our Creator Guru :D

Thank you very much!!! I already set-up remote compiler. My questions was to have clear in mind that this is the same (remote compiling with linux) as the symbian compiling under windows. As a matter of fact I have no great problems to use one platform or another, but I prefer linux. Using the simulator in ubuntu, how this can be considered near to a "real" symbian development ? Thks

NetBeans IDE also uses command line svn, and it works correctly, if I set the proxy within that IDE. If it is not possible, so I need to find a way how to set the proxy for svn tool then.

[quote author="Tobias Hunger" date="1298224767"]How am I supposed to understand that last comment? Did you cross-compile Qt Creator for Windows on a Linux box? The Linux version of Qt Creator we ship is build with gcc, not mingw... that is why I am confused:-) [/quote] Sorry let me clarify... I have a dual boot machine, Kubuntu Linux and Windows 7. In Linux downloaded from the repositories. In windows, I downloaded from the Qt web site. The windows version of Qt Creator was compiled with Visual Studio, but ships with Mingw. So when you attempt to create your own plugin, the plugin will not load with a message of: Expected build key “Windows msvc release full-config” got “Windows mingw release full-config” So I tried (on windows) to download the QtCreator source and compile with Mingw, but I am getting the errors mentioned in the original post. All I was saying is that custom plugins work perfectly in Linux because QtCreator was compiled with the same compiler, Windows however is compiled with VS, and QTCreator uses a different compiler, so plugins will not load. Is there a way to bypass the plugin signature checking without a compiling QtCreator? (Perhaps a argument or option I missed?)

Here's a little test .pro: @CONFIG(debug) { message(debug) } CONFIG(release) { message(release) } CONFIG(debug, debug|release) { message("debug, debug|release") } CONFIG(release, debug|release) { message("release, debug|release") } @ With the outputs: @$ qmake Project MESSAGE: debug Project MESSAGE: release Project MESSAGE: debug, debug|release $ qmake CONFIG-=release CONFIG+=debug Project MESSAGE: debug Project MESSAGE: debug, debug|release $ qmake CONFIG-=release CONFIG-=debug $ qmake CONFIG+=release CONFIG-=debug Project MESSAGE: release Project MESSAGE: release, debug|release @ The second parameter seems to be which configuration options to check for. If I change the last check into @CONFIG(release, debug|unrelease) { message("release, debug|release") }@ @$ qmake CONFIG+= release CONFIG-=debug Project MESSAGE: release @ If I change the check into @CONFIG(release, release) { message("release, debug|release") }@ I get @$ qmake CONFIG+=release CONFIG+=debug Project MESSAGE: debug Project MESSAGE: release Project MESSAGE: debug, debug|release Project MESSAGE: release, debug|release @ Besides specifying the items to check for, some seem to take precedence. I'm not all too sure how this is determined. Anyway, I hope this at least clarifies something.

[quote author="Volker" date="1298236788"]sigh...[/quote] Sorry, if you have the rights, you can close this post.

You are aware that Qt Creator is open source? So if you want to develop something like it, maybe you can get away with programming plugins for it? ;-) Qt Creator is actually mostly a plugin manager. Almost all the functionality is provided by plugins. So if you remove all our plugins you get a pretty basic shell to add you own plugins into.

Great to hear. Thanks.