On December 12, 2012 03:39:59 AM Tim E. Real wrote:
> Also, folks please bear with me, I'm trying to fix an infuriating side bug
> where the trackinfo patch name shows garbage characters like @u@.
> That's why all the other crap in the commit. It may or may not stay.
> Damn, I hate getting side-tracked...
Oh crud I just found out what's wrong.
Can you guys, especially those using another language, do a quick test on
the Discovery plugin for me, to verify something?
Please specifically dial-in, with the prog box, patches #48 and #49 which are
supposed to be named "Oz" and "Push".
When our midi track info patch name box converts the const char*
name string into QString, using a QString like this:
QString name(chr_name)
it gets TRANSLATED to strings displayed like "@z@" and "@u@".
I just discovered that the only way to fix it was to do this instead:
QString name = QString::fromLocal8Bit(chr_name)
QString::fromAscii() and ::fromLatin1() did NOT work.
I have to admit that all these Qt translation facilities have been
a really gray area for me over the years. Very confusing.
I've always been using toLatin1() and fromLatin1().
I mean, there are hundreds of them in MusE.
Is that the wrong one? Should they ALL be local8Bit instead?
If so, we got some serious correcting to do...
I'm guessing that if I mock-up a simple program like:
QLabel label;
const char* s = "Push";
label->setText(QString(s));
it also should not work.
Thanks.
Tim.
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
