Re: timelevel setting

[Ethan M. <merritt@u.washington.edu>]

On Sunday 14 September 2008 23:46:02 Shigeharu TAKENO wrote:
> shige 09/15 2008
> ----------------
> 
> Ethan A Merritt wrote:
> | I think that is no longer true.
> | See this note in the ChangeLogs for both 4.2 and 4.3:
> | 
> | 2008-05-08  Thomas Sefzick  <th...@us...>
> |         * src/axis.c (setup_tics):  If the user specified an explicit
> |         tic interval on a timefmt axis, do not change this by calling
> |         quantize_time_tics().
> |         Bug #1908019
> | 
> | This change has been in the CVS version for 6 months, and will be
> | included in the upcoming 4.2.4 release
> 
> I think this patch seems to decide timelevel value from the 
> interval automatically, so it may not do what I want.
> 
> To obtain "30 days" interval tics (not "1 month" interval), 
> I think we must specify the interval as 30*24*60*60 (30 days) 
> and use the timelevel value TIMELEVEL_DAYS, but the patch forces
> to use TIMELEVEL_MONTHS for "30 days" interval. So, we can not 
> obtain "30 days" interval tics even if CVS version.

You are right.  There is a problem.

Perhaps you can accomplish what you want by using some combination
of strptime() strftime() and the new iteration function for xtics
inspired by your earlier suggestion?


-- 
Ethan A Merritt