Hi André, André Wobst wrote (May 4, 2011): > The parameter ranges should indeed not harm at all. Never. What happens > here might be related to the settings, though, but it can could be > triggered elsewhere as well. The problem is, that the ticks created by the > automatic parter in combination with the manualtick you set result in a > list of only a single tick with labellevel and ticklevel being None. The > rater breaks for that. While we could create a special case in the rating > and return None here, I favor to remove those ticks completely. I decided > to not change it in the mergeticklists helper function, but filter it > explicitly in the axis code. See changeset 3051 (and 3052 due to a broken > checkin without any testing – sorry). > > You can also run your code on earlier unfixed versions of PyX by not > setting both, the ticklevel and the labellevel to be None. For example > graph.axis.tick.tick(0, 0, None) (note the second zero compared to your > None) works on unpatched versions of PyX.
The delay is perfectly understandable. Thanks for the tip on the workaround, it works a treat! I hope to see the fix in a release some time soon. It has been a while since the last one... ;-) Peace, Brendon ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ PyX-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyx-user
