Dev c error 193

I´ve tried to execute a simple instruction using wxExecute, as it was meant to substitute the system() commands.
So, instead of

I tried to use

but, while the system() function opened the notepad with the text.txt file (although showing that ugly black screen on the back of the app) the wxExecute just gave me the following error:

«Execution of command ‘text.txt’ failed (Error 193: unknown error c1)»

I tried to use wxExecute with .exe files and it seemed to have worked…

Also, for general information:
Using Dev-C++ 4.9, wxWidget 2.9, Win7 64bit

Hi,

Well, you’re trying to execute a text file, so…

Have a look at wxMimeTypesManager and wxFileType::GetOpenCommand for the way forward.

BTW, _(«text.txt») says: Please mark this string for translation. Were it successfully translated on a user’s system, the file would be unlikely to open, as the name would have changed.
On <wx2.9 you should use wxT(«text.txt»); on >=2.9 just «text.txt».

Regards,

David

Hi David, thanks for your quick reply.
I read about the wxMimeTypeManager and the wxFileType and, messing around with it, tried to open the txt file. (notice that opening the txt file is just an example, I actually want to be able to open any kind of file that the system() command would allow me to)

    wxMimeTypesManager *MIME;
    wxFileType *FT = MIME->GetFileTypeFromExtension("text.txt");
    wxExecute(FT->GetOpenCommand(wxT("text.txt")));

By doing this I actually got a fatal error in my program, so I got a bit confused on what I should actually do.

BTW, _(«text.txt») says: Please mark this string for translation. Were it successfully translated on a user’s system, the file would be unlikely to open, as the name would have changed.
On <wx2.9 you should use wxT(«text.txt»); on >=2.9 just «text.txt».

Regarding the wxString remark, I still don´t get what are strings that should be «translated».
I only use _(), _T() or wxT() whenever a function or method asks for a wxString, or I need to use some Unicode8 characters, other than that, I dont find much use to simple strings, other than non-wx related commands, such as system().

Code: Select all

    wxMimeTypesManager *MIME;
    wxFileType *FT = MIME->GetFileTypeFromExtension("text.txt");
    wxExecute(FT->GetOpenCommand(wxT("text.txt")));

By doing this I actually got a fatal error in my program

Well, you’re dereferencing a pointer, MIME, that points to random memory, so…

You could try wxMimeTypesManager *MIME = new wxMimeTypesManager;. But reading the doc, I see it says:
«Global instance of wxMimeTypesManager is always available. It is defined as follows:
wxMimeTypesManager *wxTheMimeTypesManager;»
so using that would be a better choice.

Regarding the wxString remark, I still don´t get what are strings that should be «translated».

You should mark-for-translation strings that the end-user of your app will see e.g. (quote stolen from auria’s sig):
_(«Keyboard not detected. Press F1 to continue»).
If the program runs a non-English locale (and is set up correctly), and there’s a translation available for that locale, the user will see the message in his native language.

Now consider what would happen if you did that for a filename. The good news is: it probably won’t have a translation anyway, so no harm (or good) will be done except to annoy any potential translator. But if it were a common filename e.g. ‘README’ or ‘setup’, and it did get translated, then instead of trying to load that filename, your app would instead try to load a file using the translated string as the name. Such a file is highly unlikely to exist.

wxT() and the identical _T() are nothing to do with translations. They just mark a string as being ‘long’ in a unicode build, and do nothing elsewhere. So they’re needed to make a 2.8 app compile against a unicode build.

The _() macro does wxT() internally, so you don’t need both for the same string.

DavidHart wrote:

Regarding the wxString remark, I still don´t get what are strings that should be «translated».

You should mark-for-translation strings that the end-user of your app will see e.g. (quote stolen from auria’s sig):
_(«Keyboard not detected. Press F1 to continue»).
If the program runs a non-English locale (and is set up correctly), and there’s a translation available for that locale, the user will see the message in his native language.

Now consider what would happen if you did that for a filename. The good news is: it probably won’t have a translation anyway, so no harm (or good) will be done except to annoy any potential translator. But if it were a common filename e.g. ‘README’ or ‘setup’, and it did get translated, then instead of trying to load that filename, your app would instead try to load a file using the translated string as the name. Such a file is highly unlikely to exist.

wxT() and the identical _T() are nothing to do with translations. They just mark a string as being ‘long’ in a unicode build, and do nothing elsewhere. So they’re needed to make a 2.8 app compile against a unicode build.

The _() macro does wxT() internally, so you don’t need both for the same string.

Wow, this would really create several problems with my program, as it creates and handles several files.
The problem is that I already have thousand of line of coding, using arbitrarily either _() or _T() or wxT(), so it would take a while to correct every _(), since I have no way of quickly finding where I used them improperly.

Do you think a simple «replace all _(» for «wxT(» would solve this without any consequences?
I´m a little worried about doing it and replacing some bizarre and uncalled for occurence generating a run time error bug that will be hidden for days…

Do you think a simple «replace all _(» for «wxT(» would solve this without any consequences?

Well, no translations would be better than difficult-to-debug errors. But if you ever want translations for your app, you’ll need to go through all the strings eventually.

Some of the ones that need to be translated should cluster e.g. menu labels, which makes it easier.