wxWidgets Discussion Forum

ItFinallyWorks wrote:Do you open your exe with wxFS?

Yes you do, simple as that

I never did it this way... I always used the "cat" style. cat example.exe.tmp example.zip > example.exe The cat program is originally a unix program, but there is a windows version for it. btw. this only means you don't have to compile it within you're program, and don't have to recompile ...

could you add the language to the title?

- classes always start with an upper case letter and one uppercase break on word barriers e.g. Class, DataManager etc. - member variables start with m_ or _ followed by a lowercase, and an uppercase to break for a multiple word variable such as m_variableName - methods always start with an upper ca...

Have you tried to build wxWidgets using MSVC++ 2005 Express Edition ? If yes please tell me if you did some custom settings. I would like to know how to get rid of those link errors. It worked perfectly for my when I used the command line commands.. (wxWidgets 2.8.4) Edit: when using the command li...

swapd0 wrote:For unicode applications you must use _T() instead of _().

That is not true. _T() is to tell i18n to NOT translate, _() will translate.

Did you see the class wxDir?

When you put the content into a vector (within the while loop of the sample) you are done

beside that, I think that your code is more readable when you don't need to use macro's for declaring an array.

The template provided by Code::Blocks does only support the MONOLITHIC build, in the nightly build it should be possible to use the none monolithic build. (for the nightly builds see the forum of C::B)

Did you change the driver type? The code of upCASE is using video::EDT_DIRECT3D9, but you should use the OPENGL thing (look in the documentation of Irrlicht...)

When you need a dll to distribute it with youre application, the monolithic build is the best way IMO. as less as dll's as possible. But when do you need to distribute a dll? I am working on a project which uses plugins (the same idea as Code::Blocks does.) seperate plugins and an sdk. I think it is...

ABX wrote:Sorry if my redirecting-issues-job looked like flamewar. I will try to improve my not perfect english but choosing most suitable phrases and terms is not easy

I know that problem, really I do, but thanks for exlaining it a bit for me

It is nice to have such sugestions IMO, and the code that snake is showing is just an example. It doesn't have to be used. What disapoints me is the slightly negative reaction of ABX. Well, perhaps I read it to negative, but I think you both (and of course the rest of the people) should better stop ...

priyank_bolia wrote:Also I think that wxString is totally STL complaint, you can also jsut #define wxString to std::string, AFAIK.

Perhaps this works for wxString, but does this also works for wxArray, wxHashMap, etc.?

Is it usefull to have a wrapper. or what ever, between STL and wxWidgets containers? So people can easily switch from wxString to std::string or something like that.. A is just a small step in the "right" direction, but "we" need to start somewhere ;) btw. where can I found infor...