General and Desktop

[quote author="pratik041" date="1324378815"]So what should we use in place of QPalette for the same purpose.[/quote] [quote author="pratik041" date="1324375284"]I am able to change its color through stylesheet (...)[/quote] Seems to me you already answered your own question.

Solution in a simple way @QStandardItem *itm = model->itemFromIndex(model->index(index.row(),j)); itm->setEnabled(false);@

My guess would it be because it paints on screen.

Thank you folks.

Right: the difference isn't the lack of assertions (both methods have them) -- the difference is the copy functionality. From the documentation: "at() can be faster than operator, because it never causes a deep copy to occur."

An event filter is surely fine for your purpose. Just remember to install it on the view's viewport()...

well.. I don't see OCIStmtPrepare function in QT. (I'm using ODBC3) Anyway, ther executedQuery() returned exactly same query what I input. And.. the retun value is the first thing of default asceding index. This is how I tell the hint does not work as I intened.

I do not have any problem, you actually have to adapt to changes and found them, that is great satisfaction in the program. I had difficulties at first with MAC LION, with XCode and QT longer figured out how to solve this. I put a post about that problem of architecture, in fact it is a bug in QT too. If you want to sync your MAC LION, with Xcode 4.2 and its QT can help you in some respects, however, this is working perfectly on my computer.

For me the method works. Which OS X version are you on and which Qt version do you use? And can you provide a simple, small, stripped down but complete sample that demonstrates the behavior?

[quote author="veverita" date="1324315988"] i must implement my own signal , so your example will not be good for me[/quote] Why not? There is nothing in there that requires the signal be <code>clicked()</code>, I was just using it as an example. It's easy to define your own signal, e.g. @ class MyClass : public QObject { ... public signal: void MyClassDidStuff (QString data); } @ and @void MyClass::EmitSignal () { emit MyClassDidStuff ("Hello, World!"); } @ Then, @ connect (instanceOfMyClass, SIGNAL (MyClassDidStuff(QString)), myOtherWidget, SLOT (HandleStuff(QString)));@

[quote author="Andre" date="1324284223"]Last, but not least, I think that all Qt widgets that currently have their own private undo/redo, should get a getter & setter for a [[doc:QUndoStack]] pointer, so that you can easily make their undo/redo actions part of an application-global undo/redo stack. [/quote] Amen to that.

Thanks a lot. It works! Ps. Just change terminalTextBrowser() to terminalTextBrowser. [quote author="Volker" date="1324217111"]Something like this should do the trick: @ QScrollBar *sb = ui->terminalTextBrowser()->verticalScrollBar(); sb->setValue(sb->maximum()); @ [Brain to terminal, not tested.][/quote]

I think (not tried) this is easy to solve with a simple hack like this: @ QProgressBar* progressBar = theProgressDialog->findChild<QProgressBar*>(); if (progressBar) { progressBar->setFormat("%v/%m"); //or whatever format your fancy } else { //something wend wrong. Perhaps QProgressDialog didn't use an internal QProgressBar after all? } @

[quote author="Kiut" date="1324237629"]When i use it, it set one color to the text but i want to st multi color for the text like grey and black[/quote] There is no default functionality in Qt for that. You will need to subclass and render the text yourself (perhaps via QTextDocument?)

We have since tested it and as Chris H has suggested it depends on the direction of the characters. It seems to go through the string that is set and when it finds the first char that is strictly right to left or left to right it sets the direction based on that.

So back to square 1: There is no such thing as plain text. :-)