help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Where is "colororder" defined?


From: Jaroslav Hajek
Subject: Re: Where is "colororder" defined?
Date: Thu, 2 Oct 2008 19:51:15 +0200

On Thu, Oct 2, 2008 at 4:47 PM, Samarkand <address@hidden> wrote:
>
>
>
> John W. Eaton wrote:
>>
>> On  2-Oct-2008, Samarkand wrote:
>>
>> | Thanks Ben, I appreciate your comments but I'm not sure that's the case.
>> |
>> | Please see the output I've just captured:
>> | ==========================================================
>> | address@hidden /]# octave                                                 
>> <<<  Start
>> | Octave in any directory
>> | GNU Octave, version 3.0.3
>> | Copyright (C) 2008 John W. Eaton and others.
>> |
>> | text removed for clarity .........
>> |
>> | octave:1> get (gca,"colororder")
>> | warning: get: invalid property `colororder'                          <<< 
>> Get the error
>> | message
>> | octave:2> exit
>> |
>> | address@hidden /]# cd /usr/local/share/octave/3.0.3/m/plot        <<< go to
>> the
>> | ../m/plot/ directory
>> | address@hidden plot]# octave                                              
>> <<< Start Octave
>> | GNU Octave, version 3.0.3
>> | Copyright (C) 2008 John W. Eaton and others.
>> |
>> | text removed for clarity ...........
>> |
>> | octave:1> get (gca,"colororder")
>> | <<< and it works just fine!!
>> | ans =
>> |
>> |    0.00000   0.00000   1.00000
>> |    0.00000   0.50000   0.00000
>> |    1.00000   0.00000   0.00000
>> |    0.00000   0.75000   0.75000
>> |    0.75000   0.00000   0.75000
>> |    0.75000   0.75000   0.00000
>> |    0.25000   0.25000   0.25000
>> |
>> | octave:2>
>> |
>> | =====================================================
>> |
>> | Plot ONLY works if I start Octave from the ../m/plot/ directory which is
>> | crazy!
>>
>> No, it's not crazy.  It's probably happening because you have the
>> system directories for the 3.0.0 version in your load path, so you are
>> mixing versions.  However, the current directory (".") is always first
>> in the load path, so when you start Octave in the
>> /usr/local/share/octave/3.0.3/m/plot directory, you are getting the
>> version of the plotting functions that match the version of Octave
>> that you are using.
>>
>> To verify that this is the problem, I suggest that you start Octave in
>> your home directory and type the following commands:
>>
>>   which plot
>>   path
>>
>> Is the plot function coming from the 3.0.0 directory tree?
>>
>> Does the output of path list the system directories for the 3.0.0
>> version?
>>
>> What is in your ~/.octaverc file?
>>
>> jwe
>> _______________________________________________
>> Help-octave mailing list
>> address@hidden
>> https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
>>
>>
>
> Many thanks John.
>
> I can't see any obvious evidence of using the 3.0.0. tree, here's the output
> from your suggestion:
>
> ==================================================================
> address@hidden ~]# cd ~
> address@hidden ~]# octave
> GNU Octave, version 3.0.3
> Copyright (C) 2008 John W. Eaton and others.
>
> Preamble removed for
> clarity........................................................
>
> octave:1> which plot
> plot is the user-defined function from the file
> /usr/local/share/octave/3.0.3/m/plot/plot.m
> octave:2> path
>
> Octave's search path contains the following directories:
> /usr/local/share/octave/3.0.3/m/testfun
> /usr/local/share/octave/3.0.3/m/control/base
> .
> ETC (all pointing to the 3.0.3 tree)
> .
> /usr/local/share/octave/3.0.3/m/plot
> .
> ETC (all pointing to the 3.0.3 tree)
> .
>
> octave:3> get (gca,"colororder")
> warning: get: invalid property `colororder'
> octave:4>
> =============================================================
>
> On your question of my .octaverc file well interestingly there is no such
> file on my system so am using the default environment I guess.
>

Is it possible that you're using 3.0.3 RC1? There was a nasty bug in
RC1, that prevented 'split' from working properly if two consecutive
separators occured. That could sometimes cause problems when parsing
paths. Can you try entering
`split ("a//a", "/")' into your build of Octave?


-- 
RNDr. Jaroslav Hajek
computing expert
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz


reply via email to

[Prev in Thread] Current Thread [Next in Thread]