wxWidgets Discussion Forum

wxLogNull solves the problem.

Thanks to all.

I would like to delete a file if it is not in use. I tried if (wxFileName::FileExists(file)) { wxFile f; if (f.Access(file, wxFile::write)) { wxRemoveFile(file); } } It seems, it's always possible to access the file, so I get an error message. Is there another way to check that or to suppress the er...

We have the issue on different systems, e.g. Win11 or Windows Server 2019. All systems are set to German (language and region), and also the messages should be in German. I.e., the language/region combination exists, and it does not depend on the system. The documentation of bool wxLocale::Init (int...

In our OnInit()-method we had used this code to get wx messages in system language: wxFileName path(wxTheApp->argv[0]); Locale.AddCatalogLookupPathPrefix(path.GetPath()); Locale.Init(); Since wx3.2 that dosn't work. Instead calling Init() with default parameters we have to provide Locale.GetSystemLa...

That means no solution from C::B. As a workaround I have choosen a different filename and shorter or equal than 8 characters for my INI file. I pass this filename as an argument to the executable. So it works also for debugging.

Thanks again.

That is exactly the case. Some of the subdirectories have spaces in their name. I will check the behavior in release mode tomorrow morning.

I can't explain it, hence my question here.

The differences are already in the debug build: If I start it w/o debugging, then it is okay. If I debug the same app, then I get the path in 8.3 format.

For testing I used the wxWidgets Application Template, which is created by Code::Blocks. These 2 lines I have added to the GUIFrame constructor: wxString str = wxStandardPaths::Get().GetExecutablePath(); wxMessageBox(str); The problem only occurs, if I debug the code. If I run the app in debug mode ...

We are using wxWigets 3.1.5 under Windows 10 and 11. For debug version we are using the binaries from the wxWidgets website, built with TDM-GCC 9.2. The release libraries (monolithic) are created by ourselves.

I want to read an INI file, which has the same name as the executable file but with the extension INI, and is in the same directory. For this I do the following: wxFileName filename(wxStandardPaths::Get().GetExecutablePath()); filename.SetExt("ini"); The filename of my executable file is l...

That solves the problem, now it works. The required option is -F pe-i386. Thank you, doublemax.

@ONEEYEMAN:
Yes, there are only the versions for non-static builds available. We've been using this for some time and have never had any problems with it.

Thank you again.

@doublemax: This means that resource.res is a 64bit file. That was my guess. Did you tell it to create a 32bit file? And that was the question. The help shows this: windres: supported targets: pe-x86-64 pei-x86-64 pe-bigobj-x86-64 elf64-x86-64 elf64-l1om elf64-k1om pe-i386 pei-i386 elf32-i386 elf32-...

Thanks for your replay, but I guess you can see the question mark over my head. I have downloaded and installed: - TDM-GCC 10.3 - from the wx download page the Windows binaries for TDM-GCC 10.3 (header and development files) With TDM-GCC I can build 32 and 64 bit applications. It depends on the flag...

I am using TDM-GCC 10.3 and the Windows binaries. When I try to build a simple 32 bit app, I get the following error x86_64-w64-mingw32-g++.exe -Lc:\dev\wxWidgets-3.2.0\lib\gcc103TDM_dll -o bin\Debug\Test32.exe obj\Debug\GUIFrame.o obj\Debug\Test32App.o obj\Debug\Test32Main.o obj\Debug\resource.res ...