In article <m3r7i0ahm2.fsf@...375...>,
>>>>> "Russell" == Russell E Owen
>>>>> <rowen@...529...> writes:
> We'd like to set up a set of plots that look something
> like: PPPP PPPP PPPP PPPP PPPP PPPP PPPP PPPP PPPP PPPP
> PPPP PPPP
> hhh s... hhhhh s... hhh s... hhhhhh s.....
> where - each set of Ps is a 4x4 pcolor plot representing
> signal on a 4x4 detector at a particular time. I.e. a 4x4
> array of solid blocks of gray. - h is a histogram - s is
> the left edge of a scatter plot/strip chart
> We have the basic layout, but are missing a few
> If possible, when the window is resized we'd like to: -
> Resize the histogram and scatterplots but not the pcolor
> plots. (After all, there's no detail to zoom into in a
> 4x4 pcolor plot!) - Keep the pcolor plots (Ps) square.
Perry and I have been actively discussing the need for a physical size
Axes, rather than a relative size. This doesn't exist currently, but
might help enable something like what you want -- some axes that
resize dynamically with the figure window and some that don't....
It certainly would be very useful in our case, and for many users I'm
Another useful thing for wx API, Tk API, etc. users would be a simple
and time-efficient way to say "update all these FigureCanvas objects
now". Then one could use all the power of wx, Tk, etc.'s built in layout
support, more easily mix standard GUI controls with graphs, and the
(By "time-efficient" I mean: not much worse than if all those same
graphs were on one FigureCanvas object. I have no idea if a reasonable
thing to attempt.)
> P.S. when using the TkAgg API, is this the usual idiom
> for turning off axis labels?: yls =
> self.axScatter.get_yticklabels() for yl in yls:
I just moved the set/get stuff into the Artist class so you can use it
at the API level. This is not yet in CVS, but will be soon. For now,
the way you do it will work fine, even though it may not be as pithy.
Thanks! I suspect pylab users will benefit as well!
Thank you very much for the improvements and the helpful answer.