Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Help!!! Object text display error
Forum Updated to NodeBB v4.3 + New Features

Help!!! Object text display error

Scheduled Pinned Locked Moved Mobile and Embedded
15 Posts 5 Posters 5.0k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F Offline
    F Offline
    florent.revelut
    wrote on last edited by
    #5

    on standard characters (ascii), codepage issues should not happen... especially, not with such an offset

    1 Reply Last reply
    0
    • G Offline
      G Offline
      giesbert
      wrote on last edited by
      #6

      Theoretically not, but who can guarantee?
      It's worth a try

      Nokia Certified Qt Specialist.
      Programming Is Like Sex: One mistake and you have to support it for the rest of your life. (Michael Sinz)

      1 Reply Last reply
      0
      • F Offline
        F Offline
        florent.revelut
        wrote on last edited by
        #7

        Clearly, that was my point about looking at memory : if pointed data is correct and formatting metadata as well, it's even more fun !

        1 Reply Last reply
        0
        • G Offline
          G Offline
          giesbert
          wrote on last edited by
          #8

          ok, ok.
          I see, you love to do the hard way...

          Nokia Certified Qt Specialist.
          Programming Is Like Sex: One mistake and you have to support it for the rest of your life. (Michael Sinz)

          1 Reply Last reply
          0
          • P Offline
            P Offline
            peterl
            wrote on last edited by
            #9

            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

            1 Reply Last reply
            0
            • G Offline
              G Offline
              giesbert
              wrote on last edited by
              #10

              Strange, no more ideas currently.

              Nokia Certified Qt Specialist.
              Programming Is Like Sex: One mistake and you have to support it for the rest of your life. (Michael Sinz)

              1 Reply Last reply
              0
              • F Offline
                F Offline
                florent.revelut
                wrote on last edited by
                #11

                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...

                1 Reply Last reply
                0
                • V Offline
                  V Offline
                  vinb
                  wrote on last edited by
                  #12

                  Can you try it with a checkbox or radiobutton
                  and a lineedit and post the output here?

                  1 Reply Last reply
                  0
                  • P Offline
                    P Offline
                    peterl
                    wrote on last edited by
                    #13

                    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

                    1 Reply Last reply
                    0
                    • V Offline
                      V Offline
                      vinb
                      wrote on last edited by
                      #14

                      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.

                      1 Reply Last reply
                      0
                      • G Offline
                        G Offline
                        goetz
                        wrote on last edited by
                        #15

                        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).

                        http://www.catb.org/~esr/faqs/smart-questions.html

                        1 Reply Last reply
                        0

                        • Login

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Users
                        • Groups
                        • Search
                        • Get Qt Extensions
                        • Unsolved