Internationalisation update

[thomas]

Already committed that
The app is creating the directory at startup. It still needs a wxNullLog though (is in place already too), to catch the case of a user deleting the subfolder of the currently selected language.

After adding approximately the 25.000th wxNullLog to the code, I start asking myself why we don't add one wxNullLog to CodeBlocksApp::OnRun.
All wxWidgets messages are all bullshit anyway, nobody wants to read them, there is never anything useful in them. They only hinder your workflow by throwing up a modal box that tells you something which does not matter and which you don't want to know (and which sometimes is not true, but is really just wxWidgets' bad implementation, as in "path contains too many '..'").
We're probably saving considerable code size and execution time by removing all the many wxNullLogs and inserting one early at startup.
Or, is there anyone who actually wants to read them?

[mandrav]

Or, is there anyone who actually wants to read them?

The only legit message I 'm interested in seeing is when a plugin can't be loaded because of missing symbols. The popped-up message contains the function signature that couldn't be located.
But I 'm fine with removing everything and putting one wxLogNull in main app code: I could just temporarily remove it to see what I 'm interested in .

[Pecan]

Or, is there anyone who actually wants to read them?

The only legit message I 'm interested in seeing is when a plugin can't be loaded because of missing symbols. The popped-up message contains the function signature that couldn't be located.
But I 'm fine with removing everything and putting one wxLogNull in main app code: I could just temporarily remove it to see what I 'm interested in .

If you're going to modify that section of code, could you do a DBGLOG() of that particular message or symbol that's missing.

Each time this happens, we have to comment out the two wxNullLog statements to view the missing symbol.

thanks

[mandrav]

Or, is there anyone who actually wants to read them?

The only legit message I 'm interested in seeing is when a plugin can't be loaded because of missing symbols. The popped-up message contains the function signature that couldn't be located.
But I 'm fine with removing everything and putting one wxLogNull in main app code: I could just temporarily remove it to see what I 'm interested in .

If you're going to modify that section of code, could you do a DBGLOG() of that particular message or symbol that's missing.

Each time this happens, we have to comment out the two wxNullLog statements to view the missing symbol.

thanks

Unfortunately I can't. I have tried to access the error message but it is not available...
So my solution is to comment-out those two wxLogNulls.
At least, with Thomas' proposal, we will only have to comment-out only one...

[thomas]

Unfortunately I can't. I have tried to access the error message but it is not available...
So my solution is to comment-out those two wxLogNulls.

From what I can see by looking at the wxWidgets sources, the function showing this error message

• is implemented under POSIX
• is entirely missing under Windows (cannot even find a declaration?)
• consists simply of a call to dlerror()

Thus, it would probably suffice to call dlerror() for Unices and FormatMessage(GetLastError()) for Windows, if you're interested in dumping the extended info to the debug log.

[mandrav]

Unfortunately I can't. I have tried to access the error message but it is not available...
So my solution is to comment-out those two wxLogNulls.

From what I can see by looking at the wxWidgets sources, the function showing this error message

• is implemented under POSIX
• is entirely missing under Windows (cannot even find a declaration?)
• consists simply of a call to dlerror()

Thus, it would probably suffice to call dlerror() for Unices and FormatMessage(GetLastError()) for Windows, if you're interested in dumping the extended info to the debug log.

Thanks, will have a look.