[ wxwindows-Bugs-1540852 ] wxFlexGridSizer does not appear to respect minimum sizes

[SourceForge.net]

Bugs item #1540852, was opened at 2006-08-15 12:01
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1540852&group_id=9863

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Common
Group: Must fix
Status: Open
Resolution: None
Priority: 5
Submitted By: Hank Schultz (whschultz)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxFlexGridSizer does not appear to respect minimum sizes

Initial Comment:
Okay, I'm going to leave this one up to the experts.  Sorry, no patch 
included this time.

I've verified this issue in multiple samples on wxMac, and the reason I 
went looking was visible on wxMSW as well.

I think the best example of this issue is in the artprov sample.  Open the 
sample and then choose the resources browser from the file menu.  The 
window that opens looks fine.  If you make this window larger, it still 
looks fine.  However, if you make the window smaller than its original 
size, buttons and icons begin overlapping with the list.  As the window is 
made ever smaller, the list goes off both the bottom and right edges of 
the screen.

Similar behavior is also visible in the grid and controls samples.  There 
are more, but I'm not going through all of them just to find which ones 
are not working correctly.

Oddly, the flex sizer test in the layout sample works correctly.  As a 
result, I wouldn't really even know where to start, though the issue 
*appears* to be specifically related to flex sizers.  It may not be, though.

We originally found this issue in our program, but I noticed earlier today 
that the exact same behavior is exhibited in DialogBlocks with the original 
resource file.  I then went looking in the samples and found the behavior 
there too, so I have a suspicion this isn't my fault.  If I *did* program 
something incorrectly, there are apparently a lot of other people doing 
the same thing, so we probably still shouldn't all be blamed for screwing 
up.  After all, at some point you have to blame the implementation.  ;)  
(come on people...  laugh...)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1540852&group_id=9863