wxWidgets Discussion Forum

pSizer1->Add(pSizer1_1, wxEXPAND | wxALL, 5); pSizer1->Add(pSizer1_2, wxEXPAND | wxALL, 5); pSizer1_1->Add(pText_SimScript, wxALL, 5); It looks like you are missing a parameter in there (proportion). Try this: pSizer1->Add(pSizer1_1, 0, wxEXPAND | wxALL, 5); pSizer1->Add(pSizer1_2, 0, wxEXPAND | wx...

Use the flag wxEXPAND.

It is deprecated in GCC versions before 3.4. It was undeprecated in GCC 3.4. but it's more portable to use the standard inclusion cards like Avi showed although avoid putting two leading underscores before the name as those names are reserved for the compiler's interal usage according to the ANSI st...

You really should use wxWidgets 2.6.0. I know that the default font on windows (the one that would be chosen by your first example) is Serif which is a non-TrueType font and you can only make it so small before it just stops getting any smaller. Arial should have no problems though. I've seen Arial ...

No, there isn't but I just learned for myself just how easy GDI+ is to use so if you are targeting Windows exclusively you can use GDI+. If you want something more cross platform you may want to look into using Anti-Grain.

You could try emailing Ron Lee directly and ask him (he does the Debian release packaging for wxWidgets). His address is ron <AT> debian.org.

If you are going to write one, wxRegKey will probably be of use (and is a lot easier than using the Win32 registry access API).

Digging around, there is indeed a fix for it in datetime.inl but I don't see where datetime.inl is included. I do see all the inline functions defined in datetime.h (including the one missing the msec assignment). The only place datetime.inl is mentioned is in a couple of Makefile.in's and bakefiles...

Ah, right you are. I was looking for "milli" when I looked over the Tm structure. I'm sure the developers would appreciate if you made a patch for this. It's kind of a weird oversight though.

I'm not sure, I've never done it. Has anyone on the board derived from wxFileInputStream and would like to share their insight?

You might be able to derive a new class from wxFileInputStream and update the progress bar from there. It probably wouldn't cover the time needed to decompress the image but at least you'd get the file load progress.

Weird...I could have sworn I posted a reply to this thread last night...I was groggy though so maybe I just hit Preview . All it said was check out wxDisplay but that's now covered.

I see the perl module libapache-configfile-perl (Read only. No write). My quick google search didn't reveal any C/C++ parsers but I only looked through a couple of pages of results. The Apache config format is well defined though. It shouldn't be too hard to write your own.

The structure Tm doesn't support milliseconds. Which methods are you using that end up with a call to Set(const Tm& tm)? There are 6 Set functions and without looking at the implementation, I'd assume 5 of them all call the version that accepts everything from days to milliseconds (like the version ...

I must admit, I don't understand the whole architecture of wxWidgets. I mean, after I compile the libs, why aren't they in the lib folder (they are in the "lib/vc_lib/" folder)? How can I create one single lib - or more important, how can I get the samples work with those several small lib files? (...