Why did you define QT_NO_CAST_FROM_ASCII in your .pro file?

Asked by Brian Robson Richter

I'm trying to compile your software with Qt5. I made some changes that makes it compatible with both versions of Qt but there are some methods used for conversion that doesn't exists anymore.
I removed that 'define' from .pro file and nothing bad happended, but maybe I'm missing something here.
So I woul'd like to know what kinds of side effects could happen.
My conversion is not finished yet, but when it's done I can send you a patch if you want to.
Thanks in advance.
Brian.

Question information

Language:
English Edit question
Status:
Answered
For:
4eTurnTracker Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Paul McCullagh (paul-mccullagh) said :
#2

Hi Brian,

4eTurnTracker compile with Qt 4.8. Is there any reason why you want to use 5.0?

Revision history for this message
Paul McCullagh (paul-mccullagh) said :
#4

I added QT_NO_CAST_FROM_ASCII when I added translations to 4eTT. The macro ensures that you have to qualify a string with tr() if it is to be translated, or as ASC() if no translation is required.

So the define is not essential, it is just a help.

Can you help with this problem?

Provide an answer of your own, or ask Brian Robson Richter for more information if necessary.

To post a message you must log in.