Help!!! Object text display error
-
wrote on 23 Mar 2011, 16:16 last edited by
on standard characters (ascii), codepage issues should not happen... especially, not with such an offset
-
wrote on 23 Mar 2011, 16:18 last edited by
Theoretically not, but who can guarantee?
It's worth a try -
wrote on 23 Mar 2011, 16:21 last edited by
Clearly, that was my point about looking at memory : if pointed data is correct and formatting metadata as well, it's even more fun !
-
wrote on 23 Mar 2011, 16:23 last edited by
ok, ok.
I see, you love to do the hard way... -
wrote on 23 Mar 2011, 16:32 last edited by
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
-
wrote on 23 Mar 2011, 16:46 last edited by
Strange, no more ideas currently.
-
wrote on 23 Mar 2011, 16:56 last edited by
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... -
wrote on 23 Mar 2011, 18:25 last edited by
Can you try it with a checkbox or radiobutton
and a lineedit and post the output here? -
wrote on 24 Mar 2011, 13:54 last edited by
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
-
wrote on 24 Mar 2011, 14:10 last edited by
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.
-
wrote on 24 Mar 2011, 18:43 last edited by
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).
14/15