Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Janis Papanagnou Newsgroups: comp.graphics.apps.gnuplot Subject: Re: Major and minor ticks artifact Date: Fri, 21 Mar 2014 05:52:25 +0100 Organization: Aioe.org NNTP Server Lines: 19 Message-ID: References: <53244732.8080404@gmx.eu> <5324F631.8070005@gmx.eu> NNTP-Posting-Host: 6vJrCn03lgyabPq2YdLSTw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130330 Thunderbird/17.0.5 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.graphics.apps.gnuplot:2363 On 16.03.2014 01:54, Hermann Peifer wrote: > On 2014-03-15 23:02, Janis Papanagnou wrote: >> To illustrate in a fragment of pseudo-code >> >> ## example range [ 0.0 .. 1.0 ], with inc=0.1 > > [...] Increments of 0.1 are indeed > a pain. People should simply change their thinking and coding to inc=0.125, or > apply the integer method you described. The problem with using 0.125 instead of 0.1 is that the former may not be what the end-user wants to see. After all we are looking at the visible application domain, not at a pure internal coding domain. Any discrepancy between those domains must be solved by the programs that implement a task. And since it's a well-known problem where there existed long time existing (or long forgotten?) approaches I see no obstacle that couldn't be overcome. Janis