On Thu, Apr 22, 2010 at 3:42 AM, Matthias Michler
wrote:
> Hi Gökhan,
>
> Just to make one point clear to me. Do you agree that the following is the
> expected behavior of your suggestion to use
> event.inaxes.grid(which='minormajor') after 'g'?
>
> If only the major tick grid lines are shown and
On Thu, Apr 22, 2010 at 3:25 AM, Matthias Michler
wrote:
> Hi Gökhan,
>
> with the attached test.py I generated the attached files 'pic?.png' and I'm
> sorry, I don't get the problem. For me ax.grid(False, which='majorminor')
> removes major and minor ticks on x- and y-axis.
>
> Maybe I changed so
On Wednesday 21 April 2010 19:06:09 Gökhan Sever wrote:
> On Wed, Apr 21, 2010 at 4:39 AM, Matthias Michler
>
> wrote:
> > I think it works like expected, i.e. it toggles the state of showing grid
> > lines for minor and major ticks.
> > The problem it the case were people set only major tick grid
On Wed, Apr 21, 2010 at 12:06 PM, Gökhan Sever wrote:
>
>
> On Wed, Apr 21, 2010 at 4:39 AM, Matthias Michler > wrote:
>
>> I think it works like expected, i.e. it toggles the state of showing grid
>> lines for minor and major ticks.
>> The problem it the case were people set only major tick grid
On Wed, Apr 21, 2010 at 4:39 AM, Matthias Michler
wrote:
> I think it works like expected, i.e. it toggles the state of showing grid
> lines for minor and major ticks.
> The problem it the case were people set only major tick grid lines
> ax.grid(True, which='major')
> and than press the key 'g',
On Wednesday 21 April 2010 08:10:00 Gökhan Sever wrote:
> On Tue, Apr 20, 2010 at 11:11 AM, Gökhan Sever wrote:
> > On Tue, Apr 20, 2010 at 2:42 AM, Matthias Michler
> > >
> > > wrote:
> >>
> >> Hi Gökhan,
> >>
> >> thanks for testing this small patch. Maybe one of the developers could
> >> submit
On Tue, Apr 20, 2010 at 11:11 AM, Gökhan Sever wrote:
>
>
> On Tue, Apr 20, 2010 at 2:42 AM, Matthias Michler > wrote:
>
>> Hi Gökhan,
>>
>> thanks for testing this small patch. Maybe one of the developers could
>> submit
>> it or should I place it on the patch-tracker?
>>
>>
> Usually after some
On Tue, Apr 20, 2010 at 2:42 AM, Matthias Michler
wrote:
> Hi Gökhan,
>
> thanks for testing this small patch. Maybe one of the developers could
> submit
> it or should I place it on the patch-tracker?
>
>
Usually after some pinging someone picks up the code and commits in to the
svn.
> About th
On Monday 19 April 2010 20:36:15 Gökhan Sever wrote:
> On Mon, Apr 19, 2010 at 1:31 AM, Matthias Michler
>
> wrote:
> > On Sunday 18 April 2010 00:52:57 Gökhan Sever wrote:
> > > Hello,
> > >
> > > Let say we have a figure created by:
> > >
> > > plt.plot(range(100))
> > >
> > > On WX backend plt.g
On Mon, Apr 19, 2010 at 1:31 AM, Matthias Michler
wrote:
> On Sunday 18 April 2010 00:52:57 Gökhan Sever wrote:
> > Hello,
> >
> > Let say we have a figure created by:
> >
> > plt.plot(range(100))
> >
> > On WX backend plt.grid(1) or key "G" responds finely for turning on/off
> the
> > grid lines.
On Sunday 18 April 2010 00:52:57 Gökhan Sever wrote:
> Hello,
>
> Let say we have a figure created by:
>
> plt.plot(range(100))
>
> On WX backend plt.grid(1) or key "G" responds finely for turning on/off the
> grid lines. However when I log-scale both axes then plt.grid(1 or 0) or "G"
> doesn't res
Hello,
Let say we have a figure created by:
plt.plot(range(100))
On WX backend plt.grid(1) or key "G" responds finely for turning on/off the
grid lines. However when I log-scale both axes then plt.grid(1 or 0) or "G"
doesn't respond on minor grid lines.
Is there a way to control this behavior?
12 matches
Mail list logo
