[Matplotlib-users] Re: funny window behavior

[Steve C. <ste...@ya...>]

On Tue, 2005-02-01 at 20:17 -0800, Darren Dale wrote:
> I am working in interactive mode, with the GTKAgg backend. When I make a 
> figure, I was not able to resize it on the screen. I tried changing my dpi 
> and default figure size in .matplotlibrc, and now I can increase the figure 
> size, but not decrease it passed its original size. I changed 
> my .matplotlibrc back to its original configuration, and the same behavior 
> persists: I can increase the figure size, but not decrease it passed the 
> original size. This is also true for the GTK backend, but not for WXAgg.
> 
> I rebuilt my atlas libraries today, along with Numeric, and numarray. I dont 
> think that should have anything to do with it, but I rebuilt gtk+, pygtk, and 
> matplotlib just in case. All are the latest version. 
> 
> Everything else seems to work, minimizing, maximizing, closing, but not 
> resizing. Does anyone have a suggestion as to what is wrong, or what I might 
> check?

Its related to the way the FigureCanvasGTK is implemented using
self.set_size_request() - it sets the widgets minimum size.
 
When resizing the FigureCanvas on my system I notice:
GTK   sets a FigureCanvas size that can only be increased.
QtAgg sets a FigureCanvas size that can be increased or decreased
TkAgg sets a FigureCanvas size that can be increased or decreased to a
minimum (of perhaps 400 x 300 pixels)
Wx I do not have, is it like Qt or Tk or is there a 4th variation?

I looked at changing GTK so the FigureCanvas could be decreased a while
ago but the problem is that while the axes scale/shrink nicely the text
stays the same size and becomes misaligned or clipped and gives an odd
looking graph. Perhaps thats why Tk allows you shrink the window but
only to a certain size.

Matplotlib currently has 3 (or more) ways of handling window resizing,
which one of these behaviours is 'correct' or most desirable?

Regards
Steve