[LIBISIS-code-tickets] [LIBISIS] #30: Behaviour of default values

[LIBISIS Library and Applications]

#30: Behaviour of default values
---------------------------+------------------------------------------------
Reporter:  Dean Whittaker  |        Owner:  Dean Whittaker
    Type:  enhancement     |       Status:  assigned      
Priority:  major           |   Resolution:                
Keywords:                  |  
---------------------------+------------------------------------------------
Old description:

> The current behaviour for default values is that, once plotted, a graph
> type will hold it's own set of default values, which when changed only
> apply to that graph type.. i.e.
>
> >> acolor('green')
> >> ds(w1)
> >> acolor('red')
> >> dl(w2)
>
> would give a green line plot of w2. However, a better syntax would
> probably be that default values hold for all types of graph - otherwise,
> if I have other graphs open, how do I use acolor to change the color of
> the next plot I make (if it isn't the same graph type)?
>
> A simple solution would be to change the default value routines so that
> they can accept either a global (by default) or a name and tag, so acolor
> will alter everything if given on it's own, or a specific graph type if
> given with a name and tag. This seems more intuitive.
>
> Will change the routine, without comitting and test to see if this does
> make more sense.

New description:

 The current behaviour for default values is that, once plotted, a graph
 type will hold it's own set of default values, which when changed only
 apply to that graph type.. i.e.

 ~>> acolor('green')

 ~>> ds(w1)

 ~>> acolor('red')

 ~>> dl(w2)

 would give a green line plot of w2. However, a better syntax would
 probably be that default values hold for all types of graph - otherwise,
 if I have other graphs open, how do I use acolor to change the color of
 the next plot I make (if it isn't the same graph type)?

 A simple solution would be to change the default value routines so that
 they can accept either a global (by default) or a name and tag, so acolor
 will alter everything if given on it's own, or a specific graph type if
 given with a name and tag. This seems more intuitive.

 Will change the routine, without comitting and test to see if this does
 make more sense.

-- 
Ticket URL: <http://trac.libisis.org/code/ticket/30#comment:2>
LIBISIS Library and Applications <http://www.libisis.org/>
LIBISIS Library and Applications