From: Stephen W. <ste...@cs...> - 2004-07-15 22:40:49
|
As a new user of matplotlib, I'm surprised I haven't seen this mentioned, offhand, in the mailing list archive. I am not seeing the redraw or close widgets on the plot windows I produce. The platform is Fedora Core 1, although I built on RHEL3 because matplotlib-0.60-2 won't build on FC1 (some problem with tk-devel, apparently). -- Stephen Walton <ste...@cs...> Dept. of Physics & Astronomy, Cal State Northridge |
From: John H. <jdh...@ac...> - 2004-07-19 15:48:28
|
>>>>> "GStephen" == Stephen Walton <ste...@cs...> writes: GStephen> As a new user of matplotlib, I'm surprised I haven't GStephen> seen this mentioned, offhand, in the mailing list GStephen> archive. I am not seeing the redraw or close widgets on GStephen> the plot windows I produce. The platform is Fedora Core GStephen> 1, although I built on RHEL3 because matplotlib-0.60-2 GStephen> won't build on FC1 (some problem with tk-devel, GStephen> apparently). Your post says you are a new user but the content suggests you've used matplotlib before. In early versions there was both a redraw button and a close button. The former was there because sometimes the figure would get into an inconsistent state (after exposes, or resizes for example) but these problems were fixed and I no longer saw a need for it. The close button was dropped after Steve Chaplin pointed me to some user interface design guidelines that argued close buttons should never be placed on toolbars. So it is by design that these are missing. Is this a problem for you? As for the FC1 problem, perhaps Fernando Perez can comment - I believe he has used matplotlib with FC1. I have no experience here. JDH |
From: Stephen W. <ste...@cs...> - 2004-07-19 16:41:53
|
On Mon, 2004-07-19 at 08:24, John Hunter wrote: > >>>>> "GStephen" == Stephen Walton <ste...@cs...> writes: > > GStephen> I am not seeing the redraw or close widgets on > GStephen> the plot windows I produce. > > Your post says you are a new user but the content suggests you've used > matplotlib before. I have played with version 0.50 a bit before, but I asked about the "missing" widgets because they're still in the online tutorial. Plus, I had thought the redraw button would be a convenient way to reset a plot to its default after zooming and/or scrolling in one or the other axis. This last function is one I actually need, but I was unable to see anywhere in the documentation how it might be done. > As for the FC1 [compile] problem, This turned out to be SOE (Stupid Operator Error). I didn't have the tk-devel and tcl-devel packages installed. Unfortunately the lack of tk.h and/or tcl.h causes so many error messages in the compile that the line complaining about their lack is easy to miss. Not a matplotlib problem, I hasten to add. Thanks for the responses. |
From: John H. <jdh...@ac...> - 2004-07-19 17:52:27
|
>>>>> "Stephen" == Stephen Walton <ste...@cs...> writes: Stephen> I have played with version 0.50 a bit before, but I asked Stephen> about the "missing" widgets because they're still in the Stephen> online tutorial. Plus, I had thought the redraw button Stephen> would be a convenient way to reset a plot to its default Stephen> after zooming and/or scrolling in one or the other axis. Stephen> This last function is one I actually need, but I was Stephen> unable to see anywhere in the documentation how it might Stephen> be done. Thanks for letting me know about the tutorial problem. As for resetting the axes to the original view, redraw would not have done that. In the next generation toolbar, I might be able to add a button to support that. It already has a forward / back button to navigate between previous views. By clicking back enough times, you'll get back to your original view. Still, if you are deep enough in, a "reset" button might be nice. Stephen> This turned out to be SOE (Stupid Operator Error). I Stephen> didn't have the tk-devel and tcl-devel packages Stephen> installed. Unfortunately the lack of tk.h and/or tcl.h Stephen> causes so many error messages in the compile that the Stephen> line complaining about their lack is easy to miss. Not a Stephen> matplotlib problem, I hasten to add. Yep, you have to train yourself to find that first error, the rest are often meaningless. JDH |
From: Stephen W. <ste...@cs...> - 2004-07-19 20:56:17
|
On Mon, 2004-07-19 at 10:28, John Hunter wrote: > As for > resetting the axes to the original view, redraw would not have done > that. In the next generation toolbar, I might be able to add a button > to support that. It already has a forward / back button to navigate > between previous views. Er, it does? I don't see them, at least not with either the default backend on FC1, which I'm guessing is GTK, nor with the TkAgg one. Incidentally, the on line .matplotlibrc example file still has the "toolbar" keyword, which is gone, and is missing the "datapath" one. -- Stephen Walton <ste...@cs...> Dept. of Physics & Astronomy, Cal State Northridge |
From: John H. <jdh...@ac...> - 2004-07-20 14:08:19
|
>>>>> "Stephen" == Stephen Walton <ste...@cs...> writes: Stephen> On Mon, 2004-07-19 at 10:28, John Hunter wrote: >> As for resetting the axes to the original view, redraw would >> not have done that. In the next generation toolbar, I might be >> able to add a button to support that. It already has a forward >> / back button to navigate between previous views. Stephen> Er, it does? I don't see them, at least not with either Stephen> the default backend on FC1, which I'm guessing is GTK, Stephen> nor with the TkAgg one. Sorry for the confusion - when I sat "it already has...", I'm referring to the next generation toolbar that is under development in CVS. Only GTK and GTKAgg have a prototype version of the new toolbar in CVS. For the record, the default backend in the src distributions (*.tar.gz and *.zip) is GTKAgg. For win32, the default backend in TkAgg. Stephen> Incidentally, the on line .matplotlibrc example file Stephen> still has the "toolbar" keyword, which is gone, and is Stephen> missing the "datapath" one. Which rc file are you referring to? There is no reference to the toolbar option in the 0.60.2 release, though it is in CVS and on the web (should fix that one, though it is listed as experimental). The datapath was intentionally omitted - it exists for those who want use it to set the data path but for most users the default is OK. I just changed this in my dev tree to include a commented out reference to it to alert users that it is there. Thanks, JDH |