Qt Creator and other tools

@MrLibya super Now its easy to reproduce [image: OU4M5j.png]

Hi, qt3to4 is only available in Qt 4. Note that Qt 4 offered the Qt3Support module to help porting. Don't use it at all while porting. Qt 5 completely dropped that module as it was only meant to help gradual migration to Qt 4.

Hi and welcome to devnet, That's a driver that is not build by default. You have to do it yourself. For the Qt sources, you can download them through the Maintenance Tool.

i just found fontSizeMode: Text.VerticalFit. This will try to fix sizes

You can't use int64 or unsigned int with QIntValidator. You'll need to create your own validator for that by subclassing QValidator and implementing fixup() and validate().

AFAIK, qmake works with the Windows command line. The fact that you're using MinGW doesn't influence in that respect. Do you have any special shell on your machine ?

@maydin AFAIK the include path definition is missing. Without project creator does not know how you plan to compile it later on. Therefore, some of the hinting is missing. The background is that Qt creator is an IDE where you can easily change between different tool chains. E.g. you can use an old compiler version and do the compilation and at next you may use a newer compiler version and compile the same code. Not sure what an alternative for gcc would be on linux, but on windows, you can use with one compile run MinGW (gcc derivate) and with some clicks you change everything and do a compile with the microsoft compiler. All this is defined through so-called kits. Changing a kit to another do also change the hinting and stuff. However, you have no kit defined therefore creator does not know how and what to "hint". Certainly you can use creator as pure editor, but that provides some hick-ups with reduced support (e.g. hinting). For your case you can add a project file for defining the requried and do the compilation from a terminal lateron. However, you miss out quite a lot of stuff helping you otherwise.

Hi, Because you haven't called next after your query ran. See the examples in QSqlQuery documentation details.

I'm not aware of any. qmake syntax is quite easy, though, so I never searched for it.

@hskoglund: Yes! Thank you! That did the trick. I had no idea that ESC closes these windows. Thanks again.

@hskoglund thx it work :)

@Amir-Afendin I think to get 90% of desktopRect's size so that the widget size gets adjusted as per the desktop screen size? 0.9 = 90/100

Hi, Because that's a method of QTableWidget. If you want to use a QTableView then you have to interact with the model you set on the view.

yes the ctrl+shift+r -> Refactor -> Rename is pretty dangerous as it also change inside Qt source files. It does show the files that will be changed so it can be checked/validated but if many hits, it's possible to miss and the result can be quite frustrating. [image: zA1XOW.png] But I guess you only do it once... ;)

@SGaist yes thx :)

@raven-worx thx :)

@raven-worx : Thxs for your fast response! I tried the following: 1.) Restart computer and start afterwards Qt-Creator -> then it works for a while but nevertheless the failure comes back 2.) Rename the filename.qml to _filename.qml -> same as above 3.) Change from "Build Debug" to "Build Release" -> same as above 4.) "Clean Project" + "Run" -> same as above 5.) As you ment and I overlooked, described in the bugreport, everytime I insert a new .qml file I start "Run qmake" -> it seems that it work, yep!!! Hopefully its a sustainable solution/workaround. Best greetings...

Hi, You're not opening your database and also not doing any checks to see whether your query ran successfully. Also, since you are only giving the name of the database file, it will be created in the same folder as the application unless you already provide that file.

If you want to create classic Qt GUI application you should choose Qt Widgets Application. Or, if you are familiar with web front-end development ( particularly, JavaScript and JSON), then Qt Quick Application. In my personal opinion the latter is more preferable because it is easier, more flexible and based on W3C standarts. P.S. Reference Qt documentation is gorgeous, consider to use it instead of doubtful tutorials.

Well, I just realized that I can run qmake from a terminal and it will generate a Makefile -- it's the default behavior. :)