[redirecting back to list. keep the discussions on-list, folks.]

PL LAMBALLAIS wrote:
> Well, markers type don't change. :-/
> 
> Try this:
> http://www.parx.net/cgi-bin/samples/bob_1.pl
> and
> http://www.parx.net/cgi-bin/samples/bob_2.pl
> 
> (force refresh as it display a generated GIF so running the second
> script can display the GIF from the first one).
> 
> The only difference is that for bob_1 I use:
> $my_graph->set(
>       markers => [1,2],
>       marker_size => $marker_size,
> );
> and in this case, markers types are OK and change according to the
> values. 
> 
> and for bob_2
>       markers => [1,2],\@tab,

This is *not* what you originally posted. This syntax is wrong, obviously.

It should be:

      markers => \@tab,

> 
> As you can see, no Error 500, the GIF is generated, but the markers
> are not displayed.
> 
> No very cool.
> 
> PLL
> 
> 
> 
> Bob Showalter a *crit :
> > 
> > PL LAMBALLAIS wrote:
> > > Hello,
> > > 
> > > 
> > > I'm working with a GIF generator and I've a little problem using
> > > array as parameters: 
> > > 
> > > This call works perfectly:
> > > 
> > >       $my_graph->set(
> > >               markers => [1,2],
> > >       # kind of markers (here, 2 markers)
> > >               marker_size => $marker_size,            # size of
> > >               markers );
> > > 
> > > As I use a variable as parameter for "marker_size", I want to do
> > > the same for "marker". 
> > > 
> > > So I try:
> > > 
> > >       $markers = "1-2";
> > >       @tab_tmp = split("-",$markers);
> > > # Here I have the same thing that:    @tab_tmp = ("1","2"); # and
> > > thats' OK. 
> > > 
> > > # And now, using the array as parameter:
> > >       $my_graph->set(
> > >               markers => \@tab_tmp,
> > > # kind of markers
> > >               marker_size => $marker_size,            # size of
> > >               markers );
> > > 
> > > But this don't work. I'm sure of getting the righ value in the
> > > array, so the problem came from "\@tab_tmp". What is the right
> > > syntax? 
> > 
> > That syntax looks OK, so there must be something else going on. You
> > need to define "don't work".


-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to