[quote author="neFAST" date="1308696036"]I can understand this. However I don't know what I should request. I just said
[quote author="neFAST" date="1307718701"]On win7, qsettings are stored in appData/Roaming while QDesktopServices::DataLocation points to appData/Local[/quote] but is it a bug? What should be the correct behavior?[/quote]
I do not have an idea. I would have to read on that topic first. Maybe some googling gives you more information. Sorry that I cannot give you a more useful answer.
I think I have found some kind of workaround: if I ignore() QEvent::TabletMove events, they get transformed into mouse event, so I only have significant mouseevent instead.
I would recommend to use Qt's SQL classes for storing and retrieving data. They should handle the conversion pretty good and you can operate on QStrings directly. The SQLite driver of Qt should be available with all binary installations.
[quote author="rufus359" date="1308781208"]UPDATE: Apparently Qt is not able to find the fonts on my machine and insists on using its own. Creating a symbolic link to a font that supports Japanese characters in the "[QtDir]/lib/fonts" folder solved the problem.[/quote]
Cheers for the update, and welcome to the devnet :)
bq. A plugin is simply a shared library
I have a "bad habit" think that shared library is exactly an executable just with unresolved external links. That assumes resources are located inside this executable. Probably you know where from this habit appeared... This is my first time working with plugins in Qt. Need to change some conceptions.
Someone from the StackOverflow forum answered my question very nicely:
http://stackoverflow.com/questions/6433933/qtcpclient-successfully-connects-but-not-to-my-server-where-is-it-connecting
bq. While QTEST_MAIN creates a QApplication and runs all your tests, it does so sequentially and not with an event loop. Therefore, while your socket can indeed connect to the server (meaning qTestSocket->waitForConnected() returns true), since the app doesn't return to an event loop, the QTcpServer's signal will not get emitted, and TcpCommSocketTest::connectDummyServer() never gets called.
Try adding a call to qApp->processEvents() at the end of initTestCase(). It should let connectDummyServer() be called.
It seems that I needed to add a qApp->processEvents() call in my initialization function.
I removed uft8_bin from table option tab in MySQL Admin. but each time I insert data using MySQL Query Browser, colliding method is added to all tables of database.
I'm going to create re-database with mysql cli.
Thank you very much :-)
UPDATED:
I do everything from beginning, and remove every colliding method. Now everything works fine:
!http://s1.picofile.com/file/6846154924/screenshot9.png()!
Thanks again.
I just found a solution :
" QAbstractItemView {"
"selection-background-color: rgba(0,0,0,0);"
It makes the cream background disappear thanks to transparncy.
Hope it could help someone.
Thnaks for help anyway.
This wiki article describes a class you can use as editor main window class. it enables associating file extension to the exe during first start, like MFC does. It also enables MDI handling do newly opened files are opened in the running process.
But this code only works for windows, definitly.
[quote author="loladiro" date="1308738072"]After reading the sources:
@
QVariant(float f) { d.is_null = false; d.type = QMetaType::Float; d.data.f = f; }
@
Yes it is! Although you could use int QVariant::userType() if you feel more comfortable comparing to an int.[/quote]
Thanks.
[quote author="Andre" date="1308739392"]Note that in Qt 5, the distinction between QVariant::Type and QMetaType::Type will most likely go away.[/quote]
That's a good news...
ok i figured out how to remove correctly, i went into the folder of each sdk and ran the maintainance gui from the command like as sudo
seems like since i installed the sdk as sudo, the maintenance gui from the menu is not getting run in sudo mode and therefore hangs
i also had to select, 'remove old qtcreator settings' when installing sdk1.1.2, otherwise it was still pointing to the wrong (older) folder for qmake