# Problem with encapsulated text in shaded node with tikz

I'm working with the TikZ package and I noticed that even though I get a correct pdf file with this .tex file (found in this forum):

\documentclass{article}
\usepackage{tikz}
\begin{document}
\tikzstyle{ball} = [circle,shading=ball, ball color=red!80!white, minimum size=1cm]
\begin{tikzpicture}
\node [style=ball] {blah blah};
\end{tikzpicture}
\end{document}


if for example I change the colour from red to blue and I open the pdf file, keeping open the first one, there isn't the expected colour background, but if I close both the files and I open one of them the first one is correctly visualized, whereas the second is not...

Could someone tell me the reason of this problem?... and how to solve it...

PS: I'm working with MiKTeX and TeXnicCenter on Windows

-
There is only one pdf per tex file. If you change the tex file then the pdf will change as well. If you do unexpected things like open up another view of the same pdf file you might catch it sandwiched around changes to the tex file. But that's temporary--eventually all views will reflect the updated tex file. Is this at all relevant or do I completely misunderstand what you want to have happen? –  Matthew Leingang Dec 6 '10 at 16:21
I guess it's a problem with the reader. Perhaps it's the Adobe Reader, google tikz shading adobe reader (or combine with bug) gives some results. Try another pdf Reader. I can confirm that the Adobe Reader doesn't show the color but the TeXworks previewer does, on my system. –  Stefan Kottwitz Dec 6 '10 at 16:38
I'm working with Acrobat Reader 9.3 (whereas I do not have this problem with an older version...) and even if I open my pdf file got by LATEX after any pdf file I get this problem. This could be very unconfortable especially when you have to send your file to other people unless you decide to say sorry but first all you have to close all the other pdf files or you have to use a specific version of Acrobat Reader... –  Arianna Dec 6 '10 at 17:39
I cannot reproduce this behavior with Adobe Reader 10.1.7 or Sumatra PDF 2.3.2. So if this was a bug in Adobe Reader it is fixed in the current version. –  Alexander Jul 31 '13 at 12:15