Favicon

problem with mark=ball

Hi,

Using something like

 \begin{scope}[mark=ball,xscale=0.15,yscale=0.1,mark size=3mm,mark options={xscale=2,yscale=3}]
    \draw[ball color=darkblue,color=darkblue] plot coordinates {\TikZdataA};
    \draw[ball color=darkred] plot coordinates {\TikZdataE};
 \end{scope}

gets me a line (ok), ball marks at the coordinates (ok), and a filled
polygon along the coordinates (definitely not ok).  I'd be glad if you
could tell me where my mistake is.

TIA,

Juergen

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
pgf-users mailing list
pgf-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pgf-users
Till Tantau | 1 Aug 11:15
Picon
Favicon

Re: problem with mark=ball

Hi!

the problem is that you gave the "ball color" option to the \draw  
command. The ball color option switches shading on, implicitly.

What you actually want is to give the "ball color" option to the  
"plot" command as in

     \draw plot[ball color=red] coordinates {(2,2) (-30,4) (5,20)};

I admit I was also surprised when I tried your code, but when one  
thinks about this very, very carefully, it turns out that the TikZ  
behaviour is actually quite correct/logical. (Note that you might  
want to fill a plot with a shading using "ball color" with the \draw  
command and also have ball marks on the plot in a different color;  
here you need the "ball color" option with the plot command)

Best regards,
Till

Am 01.08.2007 um 10:06 schrieb Goebel, Juergen, OPES26:

> Hi,
>
> Using something like
>
>  \begin{scope}[mark=ball,xscale=0.15,yscale=0.1,mark size=3mm,mark  
> options={xscale=2,yscale=3}]
>     \draw[ball color=darkblue,color=darkblue] plot coordinates  
> {\TikZdataA};
>     \draw[ball color=darkred] plot coordinates {\TikZdataE};
>  \end{scope}
>
> gets me a line (ok), ball marks at the coordinates (ok), and a filled
> polygon along the coordinates (definitely not ok).  I'd be glad if you
> could tell me where my mistake is.
>
> TIA,
>
> Juergen
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a  
> browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/ 
> _______________________________________________
> pgf-users mailing list
> pgf-users <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pgf-users

--
Prof. Dr. Till Tantau <tantau <at> tcs.uni-luebeck.de>
http://www.tcs.uni-luebeck.de

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
Favicon

Re: problem with mark=ball

> Till Tantau wrote:

> the problem is that you gave the "ball color" option to the \draw  
> command. The ball color option switches shading on, implicitly.

ACK

> What you actually want is to give the "ball color" option to the  
> "plot" command as in
> 
>      \draw plot[ball color=red] coordinates {(2,2) (-30,4) (5,20)};

Thanks, works fine.

> I admit I was also surprised when I tried your code, 

:-))

> but when one  
> thinks about this very, very carefully, it turns out that the TikZ  
> behaviour is actually quite correct/logical. 

I'd never doubt about that!  I'm still a newbie with TikZ and so
some details of the -- rather complex -- concept are still strange
to me.

Thanks a lot,

Juergen

NB: This monday I asked a question about "set a text along a curvaceous 
contour". I'm not sure, if that mail reached the list ...

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
Björn Steffen | 2 Aug 17:01
Picon

Keeping the \tikzstyle command

Hi Till Tantau,

I noticed that you introduced a new key management facility into pgf.
This is great because the new system is a lot more powerful. Specially
for library writers the new pgfkeys package is useful. But I consider
the new syntax for specifying styles too cumbersome for the "ordinary"
user.
    \tikzset{my style/.style={some options,...}}

I suggest keeping the old syntax,
    \tikzstyle{my style}=[some options,...]
since it is much easier to read and understand. The new syntax would
be for the more "advanced" users and library writers.

Just my thoughts about the topic. Keep up the wonderful work on TikZ.

Best regards,
Björn
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
pgf-users mailing list
pgf-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pgf-users
Till Tantau | 2 Aug 17:27
Picon
Picon

Re: Keeping the \tikzstyle command

Hello everyone,

I'm a bit undecided on this.

First, for compatibility reasons \tikzstyle will be around  
indefinitely, so the real question is what will be better for new code.

The reason I'm trying to kick out the \tikzstyle is that I would like  
to encourage people to keep style settings as local as possible. So,  
normally, style definitions should be given at the beginning of a  
picture as in

\begin{tikzpicture}
   [some options,
    first style/.style={blah},
    second style/.style={blub}]
   ...
\end{tikzpicture}

Then, if the tikzpicture is moved/copied/whatever, the styles are  
moved around with it. Furthermore, styles given as options always  
apply to the whole scope and end with it automatically.

However, I'm also not quite sure whether this argument is all that  
convincing. Global styles still have to be set globally using  
\tikzset anyway...

I have started to change the whole documentation code to the new  
system and it does not seem to change the readability much.

Anyway, you can now say things like

\tikzstyle{my style}=[draw=#1,fill=#1!20]

and I have actually extended the syntax of \tikzstyle so that one can  
also provide a default argument as in

\tikzstyle{my style}[red]=[draw=#1,fill=#1!20]

More comments on this would be appreciated.

Best regards,
Till

Am 02.08.2007 um 17:01 schrieb Björn Steffen:

> Hi Till Tantau,
>
> I noticed that you introduced a new key management facility into pgf.
> This is great because the new system is a lot more powerful. Specially
> for library writers the new pgfkeys package is useful. But I consider
> the new syntax for specifying styles too cumbersome for the "ordinary"
> user.
>     \tikzset{my style/.style={some options,...}}
>
> I suggest keeping the old syntax,
>     \tikzstyle{my style}=[some options,...]
> since it is much easier to read and understand. The new syntax would
> be for the more "advanced" users and library writers.
>
> Just my thoughts about the topic. Keep up the wonderful work on TikZ.
>
> Best regards,
> Björn
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a  
> browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> pgf-users mailing list
> pgf-users <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pgf-users

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
Björn Steffen | 2 Aug 17:58
Picon

Re: Keeping the \tikzstyle command

Hi Till and everyone,

> The reason I'm trying to kick out the \tikzstyle is that I would like
> to encourage people to keep style settings as local as possible. So,
> normally, style definitions should be given at the beginning of a
> picture as in
>
> [...]
>
> Then, if the tikzpicture is moved/copied/whatever, the styles are
> moved around with it. Furthermore, styles given as options always
> apply to the whole scope and end with it automatically.
>
> However, I'm also not quite sure whether this argument is all that
> convincing. Global styles still have to be set globally using
> \tikzset anyway...

I totally agree that options should be kept local. But there are also
cases when global options are needed. For example to keep the look of
all the pictures of a document consistent. If I have any further ideas
on this, I'll let you know.

The readability is for me not a problem. Just thought it might be
problematic for new users. But in the long run, I guess it doesn't
matter.

> Anyway, you can now say things like
>
> \tikzstyle{my style}=[draw=#1,fill=#1!20]
>
> and I have actually extended the syntax of \tikzstyle so that one can
> also provide a default argument as in
>
> \tikzstyle{my style}[red]=[draw=#1,fill=#1!20]

Perfect! This is great and very useful. For specifying styles with a
default argument, the \tikzstyle way seems a lot easier.

Best regards,
Björn
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
pgf-users mailing list
pgf-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pgf-users
Ignasi Furió | 3 Aug 15:02
Picon
Picon
Favicon

tikz terminal for gnuplot

Hi all,
	
I have to prepare a presentation with beamer. I have reploted several  
block diagrams with tikz but I also
have to include a lot of semilogarithmic 'gnuplot' plots. I did them using  
'epslatex' terminal but I know that
with some limitations is possible to plot also with tikz.

I also have found 'http://peter.affenbande.org/gnuplot' where is possible  
to download a 'tikz+lua' terminal for gnuplot.

I never compiled gnuplot over windows neither used or installed lua, so my  
questions are:

Anybody has used this terminal over windowsxp? How?

What will be the problems trying to 'replot' my results with tikz?

Thank you,

	Ignasi

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
Picon

Re: Keeping the \tikzstyle command

"Björn Steffen" <bjoern.steffen <at> inf.ethz.ch> writes:

> Hi Till and everyone,
>

[...]

> I totally agree that options should be kept local. But there are also
> cases when global options are needed. For example to keep the look of
> all the pictures of a document consistent. If I have any further ideas
> on this, I'll let you know.

I'd second that too.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
Mark Wibrow | 6 Aug 09:00
Picon
Picon
Favicon

Re: \pgfmathreciprocal ?


Hello,

The problems conerning accuracy and efficiency of the algorithms, and what
individuals can do to change them is documented in the manual and has
already been
discussed on the mailing list. 

I'm unwilling to change \pgfmathreciprocal as it stands because it is quick
and
provides tolerable accuracy, particularly for small numbers, and I use it
heavily in
all of the newer geometric shapes.

However as one of the given examples is particularly bad, the following
change has
been made to \pgfmathdivide, and thus any parsing operation of the form X/Y:

(1) if Y is an integer TeX division is used.
(2) if X=1 \pgfmathrecipocal is used.
(3) otherwise the following equivalence is used:

   X/Y=e^(ln(X)-ln(Y))

The accuracy is improved (a bit) in (3) but it is about twice as slow. 

Until luaTeX, or something similar comes along, if you want the accuracy of
fp...you
have to use fp. 

Regards

Mark

--

-- 
View this message in context: http://www.nabble.com/%5Cpgfmathreciprocal---tf4160632.html#a12011860
Sent from the pgf-users mailing list archive at Nabble.com.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
Alain Matthes | 6 Aug 14:14
Picon
Gravatar

Re: \pgfmathreciprocal ?

Le lundi 06 août 2007 à 00:00 -0700, Mark Wibrow a écrit :
> Hello,

>    
> The accuracy is improved (a bit) in (3) but it is about twice as slow. 
> 
> Until luaTeX, or something similar comes along, if you want the accuracy of
> fp...you
> have to use fp. 

Thanks but if I can make all the operations with pgf, I prefer :) and
like you say with little numbers, the results are fine. 

> I'm unwilling to change \pgfmathreciprocal as it stands because it is
> quick and provides tolerable accuracy, particularly for small numbers

Yes in my examples I notice that \pgfmathreciprocal provides tolerable
accuracy for small numbers. Now for my next Euclidean Geometry package,
I work with a page like a square with a side of 20 cm (max), I transform
all the forms X/Y with (X/1000)/(Y/1000).

Perhaps for more accuracy and tolerable speed, it's possible to use only
numbers < 1 and for that, to use a macro that gives X/(10^n). I don't
known if a  such macro is complicated.

A last question, how to round ( 0.01) a decimal number : 15.126  with
accuracy?

Greetings and Thanks for your work

Alain Matthes (sorry for my bad english)

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
pgf-users mailing list
pgf-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pgf-users

Gmane