Help!!! Object text display error
-
Theoretically not, but who can guarantee?
It's worth a try -
Clearly, that was my point about looking at memory : if pointed data is correct and formatting metadata as well, it's even more fun !
-
ok, ok.
I see, you love to do the hard way... -
I tested
@l->setText(QLatin1String("Aba")); @even
@
main()
{
...
QTextCodec::setCodecForLocale(QTextCodec::codecForName("System"));
QTextCodec::setCodecForCStrings(QTextCodec::codecForName("System"));
QTextCodec::setCodecForTr(QTextCodec::codecForName("System"));
}
@and
@
main()
{
...
QTextCodec::setCodecForLocale(QTextCodec::codecForName("UTF-8"));
QTextCodec::setCodecForCStrings(QTextCodec::codecForName("UTF-8"));
QTextCodec::setCodecForTr(QTextCodec::codecForName("UTF-8"));
}
@all the result are the same
-
Strange, no more ideas currently.
-
Funny thing, on your screenshot, it seems to work with a button or another graphical primitive...
I'm starting to be stuck (and stunned (and damn interested)), too bad I don't have a target to start looking in depth... -
Can you try it with a checkbox or radiobutton
and a lineedit and post the output here? -
added checkbox, radiobutton and a lineedit,
!http://cdupload.com/pthumbs/large/74977/Screenshot0006.jpg(6)!
Avoid conflict, uninstalled Qt4.7 for Desktop, QtSDK 1.0, then installed QtSDK 1.1 beta, got the same result....
So, maybe it isn't complier environment problem, is target device problem???? But if so, why other applications run properly???
who knows
...OMG
-
seems like it is shifting 2 chars, so you can work around it and get the good result. But it is a strange case indeed and im very interested in the solution. If you find any.
-
It's high time for a new ticket in the "bug tracker":http://bugreports.qt.nokia.com, I would say... (and leave a link to the ticket here, please).