wxWidgets Discussion Forum

Yep. You can fix this by applying the wxVScrolledWindow parts of this patch to the version of wxWidgets you are using.

wxVScrolledWindow actually has problems with children layed out using a sizer. I've address these problems in a patch but it hasn't been applied yet. You should be able to query the actual windows about their size. Something like parent_window->GetChildren(), parent_window->GetSizer->GetItem() (not ...

I'm not quite sure what you mean by "I want the window to scroll automatically to adjust all the panels. Currently the bottom panels are not visible." Could you expand on that? If you mean that the wxVScrolledWindow isn't using the correct sizes, make sure your overload of OnGetLineHeight() returns ...

Use wxEvtHandler::Connect to connect dynamically created controls to event handlers (wxChoice and all windows/controls derive from wxEvtHandler).

Actually no. I originally wrote this over a year ago (long before that appeared in the wiki). It is, in fact, based on Bart Trzynadlowski's bin2c program (who--I'm sure--wasn't the first person to write a binary-to-C converter) but adapted for use in a wxWidgets app (by me). The orginal idea to conv...

I believe on versions of Windows before XP (98, 2000, etc.) if the alpha channel isn't 0x00 or 0xFF (on or off) for every "pixel" of the alpha channel it does this. Basically, you have to use your alpha channel as an alpha mask. If anyone knows any way around this I'd love to hear it as well.

wxImage's scaling functions are very simplistic. When shrinking, it just leaves a few rows/columns of pixels out. Growing just duplicates. ImageMagick would be a very good choice. It features a large variety of image resizing algorithms and I'm sure it produces good results. I haven't done it but I'...

I'm not sure what the error is but you will probably need to call [your wxApp derived class]::SetExitOnFrameDelete(false); By default, wxWidgets ends the application when there are no top level windows/frames remaining. If you never create one, the program will end immediately.

Yeah, it's a pointer thing. I suspect it's taking the pointer location of the string literal "0", adding the numerical value of '.' which makes the pointer point to some other string literal (since, unless I'm mistaken, they are stored in the same approximate location in executable files and end up ...

Although I don't have an answer for your question, sethjackson is correct. Destroy will free the memory. The extra stuff Destroy does is primarily delaying the actual deletion of the object until the object isn't referred to in pending messages. You don't want to be getting repaint events on a dialo...

Thanks for solving my laziness . I'll update the original post.

I use this method in my app (probably 30 images or so). Works great. XRC is another option. Another advantage of this over using the GIMP C-source option (ignoring whether it is even possible to use GIMP C-source) is you still have compressed data. Uncompressed image data can get unwieldy very quick...

You'll have to be way more specific than that if you want to get any help. Most importantly, what platform (Win32, *nix, OSX, etc.) are you on and what compiler are you using (Microsoft, gcc, etc.)?

Are you forgetting to include <wx/grid.h> somewhere before that line?

It's based on your locale settings so perhaps your locale isn't an A.M./P.M. locale for whatever reason.