Wiki Discussion

In any case, that would be really great. Writing little snippets would be easier just with the automatic parenthesis/quotes matching

Thank you, koahnig! Tero fixed it.

I had the same problem, and substitute: toAScii -> toLatin1 fromAScii -> fromASCII Works fine to me too, Thanks for sharing the code.

Ah jeez, I missed that. Thanks!

Can you show how you are configuring it ?

Cool, thanks :-)

Sorry to resume this old thread, but I can't make CheckableProxyModel work with Qt 5.2. I downloaded from git@gitorious.org:checkableproxymodel/checkableproxymodel.git the lastest version but I couldn't select or deselct the items on the treeview for the bundled example. The only changes I made was for QT5 compatibility (QT += widgets in .pro file and #include <QApplication> instead of QtGui/QApplication) Anyone succeded on using this class with QT 5.2 ? EDIT : I forgot to explain where the problem lies and when it occours. It happens only for directories and not files in the treeview. The part of CheckableProxyModel which behaves differently is @ CheckableProxyModel::TreeCheckState treeState(CheckableProxyModel::Checked); if (state == Qt::Unchecked) { treeState = CheckableProxyModel::Unchecked; } else if (state == Qt::PartiallyChecked) { qWarning() << "Unexpected new tree state."; return false; } @ It constantly prints the "Unexpected new tree state." string. By setting the @CHECKABLEPROXYMODEL_DEBUG@ define the state is set to 2 (which corresponds on PartiallyChecked on the enum Qt::CheckState) After some invstigations, I've seen that the differences in 5.1.1 source and 5.2.0 for QItemDelegate may be the source of this problem, in particular For QT 5.1.1 @QItemDelegate::editorEvent(....){ ... ... Qt::CheckState state = (static_castQt::CheckState(value.toInt()) == Qt::Checked ? Qt::Unchecked : Qt::Checked); return model->setData(index, state, Qt::CheckStateRole); } @ while for QT 5.2.0 is @QItemDelegate::editorEvent(....){ ... ... Qt::CheckState state = static_castQt::CheckState(value.toInt()); if (flags & Qt::ItemIsTristate) state = ((Qt::CheckState)((state + 1) % 3)); else state = (state == Qt::Checked) ? Qt::Unchecked : Qt::Checked; return model->setData(index, state, Qt::CheckStateRole); } @ Thank you in advance

Hi shav, Nice work! Thanks for the effort. With examples like that the wiki can grow and attract even more users.

my dns : @QString dsn=QString("DRIVER{Sql native client};server=%1;database=%2;trusted_connectivity=yes;").arg(servername).arg(dbname);@

Hi Gerolf, Thank you for the great article. However, it seems to be a little bit outdated now. Your code does not seem to work with the following combination (sorry cannot locate the problem exactly): qt5.1.0 windows 7 64-bit mingw64 gcc 4.8.0 DDE messages work if the process is already running. But DDE fails at the first startup when double-clicking the icon: It yields the Windows error message "There was a problem sending the command to the program". BTW, other posts suggest that DDE is deprecated and one should use "DropTarget" and COM instead. However, I could not figure out how to do this with activeqt, either. Any help will be appreciated… PS: On 64-bit the code (line 233-234) @ //IA64: Assume DDE LPARAMs are still 32-bit Q_ASSERT(::UnpackDDElParam(WM_DDE_EXECUTE, message->lParam, &unused, (UINT_PTR*)&hData)); @ had to be replaced to use "message->lParam" directly with no UnpackDDElParam(). This yields the command string which is otherwise corrupted.

Thanks for the info. Gotta agree, a wiki is not the ideal host for the sort of article that will become outdated like that. Maybe it could be prefaced with something to that effect rather than updated. As for Modern, that term has been used by many Microsoft evangelists so it seemed official. But I'll take your word for it unless I learn otherwise. Edit: here's some insight "http://en.wikipedia.org/wiki/Modern_UI_(design_language)#Naming_issues":undefined

[quote author="great88" date="1376933337"]Is it OK to spawn new thread inside a readyRead() handler and then access and write to tcpsockets ( from the parent thread ) from that thread ? It looks to me that this is not good because sometimes clients are not receiving data . What is the proper way to do this ?[/quote]If your TCP socket is in the parent thread, you cannot write to it from a new thread. There have been many posts about combining QTcpSocket and QThread recently. Search the forum, and you should find plenty of info.

Hi and welcome to devnet, Sounds like some sort of wizard, have a look at the QWizard documentation and for the timer part at QTimer. As a side note it's Qt, QT stands for Apple's QuickTime. Also next time, please choose a more suitable sub forum, this one is dedicated to question related to the wiki part of the site.

[quote author="cxx::qmanic" date="1372610754"][quote author="JKSH" date="1372564126"]The documentation linked from the original post is the archived version of Qt 4.7 docs, which are no longer being developed. The currently-maintained versions of Qt are Qt 5.0 (released in 2012) and Qt 4.8 (released in 2011).[/quote] Not really sure what you're saying here. The documentation I'm speaking of is located here: http://qt-project.org/doc/qt-4.8/gettingstartedqt.html and if 4.8 is still maintained then it would be nice to update the documentation accordingly so Devs can have reliable documentation to learn from.[/quote]I was saying that the issues only exist in Qt 4.7; everything that Volker, Bertus and densewater mentioned is fixed in the Qt 4.8 page that you linked. The only issue left that I can see is the anchoring, which now has a formal bugtracker ticket. nonot1's struggle with make is toolchain-specific -- Qt supports many different tools; showing all the variants of make will just clutter the tutorial. As for missing DLLs, that's a topic on deployment which has "entire pages":http://qt-project.org/doc/qt-4.8/deployment.html#platform-specific-notes dedicated to it -- it's not quite "Getting Started" material (and it's not Qt-specific either). Have I missed anything? The issues still exist in the archived Qt 4.7 docs, because that's what it is -- an archived copy, which won't (and shouldn't) be changed. [quote author="cxx::qmanic" date="1372610754"]Also I noticed in your bug report that you created a ticker for 5.0 - which still has the same anchor issue. Do both 5.0 and 4.8 "learn more" sections link to the same place? Is this what you were saying in your response thus Updating one will update the other? If so great, if not again my first point about correcting the docs for 4.8.[/quote]They don't link to the same place, as they have independent code bases. To keep the 2 versions in sync, the procedure is to push changes to Qt 5.x first, then cherry-pick important fixes over to Qt 4.8.[/quote] [quote author="cxx::qmanic" date="1372610754"]Thanks for taking the time to reply and even creating a bug report. Much appreciated.[/quote]You're welcome :) That's what a community is for!

I'd file a bug report about it in the bug tracker, section website. I doubt the current maintainers are actively monitoring the forums for these reports at the moment.

What is the name of Wiki engine again? Why it is not written at the bottom?