Adding Colour to Graph

2014-07-17
2014-09-12
  • Soumyaranjan Dash

    Hi
    I am using this :
    plot,t,c1,xtitle='Time',ytitle='SinT',background=110,linestyle=4

    It returns colour Red ???
    When i change the color index, it wont change the color.
    e.g. background= 140 (more red)
    background=160 (more red)
    background=50 (light red)

    Whatever i put there in the index, it returns the colour red in different intensities.
    What is the problem ???
    Same problem occurs to the plot when i use no 'background' command , it gives black.
    when i use 'color=40' or something, it changes the defult white colour of plot to red.

    Please Help.

     
  • Sylwester Arabas

    You can specifyi color components using hexadecimal notation, e.g.

    GDL> plot, sin(findgen(100)), background='ffdd00'x

    HTH,
    Sylwester

     
    • cosmicbruce

      cosmicbruce - 2014-09-05

      Hello All:

      There are two systems I know of for convenient colors for plotting:
      setcolors.pro, which you run at startup, which assigns several popular color names to system variables so you can say plot,data,color=!green
      The other system is fsc_colors, which I think it popular with coyote and his devotees, use like: plot,data,color=fsc_color("green").

      I cannot get either working.

      I. Sectolors Problems
      When I run setcolors I get the error, " DEVICE: Keyword parameter GET_VISUAL_NAME not allowed in call to: DEVICE"
      this is from the line: device, get_visual_name=visual, $
      get_visual_depth=depth, $
      get_decomposed=decomposed

      II. fsc_colors problems:
      When I run fsc_colors (>oplot,[5,3,8],psym=6,symsize=2,color=fsc_color("green"))
      I get the error message, "WIDGET_BASE: GDL was compiled without support for wxWidgets"
      Well, this is not true. I did > port install gnudatalanguage +wxWidgets

      So, can anyone help get one of these popular methods working?

      I should not that I can display images in color very well using "frame", which I believe is derived from "tvscl" ultimately.

      Thanks in advance,

      -Bruce

       
      • cosmicbruce

        cosmicbruce - 2014-09-05

        With a little modification, you can get setcolors working on standard Xwindows on a mac (see previous post for explanation; pro is appended as "gsetcolors/pro"). However, I did have trouble with PS output. Re-running this pro after switching to set_plot,'ps' did not work. I had to force all non-color plots with color=!black, otherwise I just got a blank page.
        -CB

        pro gsetcolors, NAMES=names, VALUES=ctindx, $
        NPLOTCOLORS=nplotcol, TABLESIZE=size, $
        $
        DECOMPOSED=decomposed, $
        SYSTEM_VARIABLES=system_variables, $
        GETINFO=getinfo, $
        SILENT=silent, $
        TEST=test, $
        START=start, $
        NOCOLORS=nocolors,$
        $
        PLOTCOLORS=plotcolors, $
        R_PLOT=r_plot, $
        G_PLOT=g_plot, $
        B_PLOT=b_plot, $
        $
        PSEUDO256=pseudo256, $
        $
        _REF_EXTRA=extra
        ;+
        ; NAME:
        ; SETCOLORS
        ;
        ; PURPOSE:
        ; To set up device independent line plot colors. Designed to
        ; work correctly on both X Window and PostScript devices.
        ;
        ; CALLING SEQUENCE:
        ; SETCOLORS [, NAMES=string array][, VALUES=array][,
        ; NPLOTCOLORS=variable]
        [, TABLESIZE=variable][,
        ; DECOMPOSED={0|1}]
        [,/SYSTEM_VARIABLES][,
        ; /GETINFO]
        [,/SILENT][,/TEST][,/START][,
        ; PLOTCOLORS=string array, R_PLOT=array, G_PLOT=array,
        ; B_PLOT=array]
        [,/PSEUDO256]
        ;
        ; INPUTS:
        ; None.
        ;
        ; OPTIONAL INPUTS:
        ; (You can provide your own set of line plot colors, but you
        ; must provide all four of the following keywords and they
        ; must all have the same size! (See EXAMPLE.) If omitted,
        ; a set of 12 basic colors is used.)
        ;
        ; PLOTCOLORS = A string array of user-defined line plot color names.
        ;
        ; R_PLOT = The RED values of line plot colors.
        ;
        ; G_PLOT = The GREEN values of line plot colors.
        ;
        ; B_PLOT = The BLUE values of line plot colors.
        ;
        ; OUTPUTS:
        ; None.
        ;
        ; OPTIONAL OUTPUTS:
        ; NAMES = Returns a string array of the line plot color names.
        ;
        ; VALUES = Returns an array of the color table indices (8-bit) or
        ; 24-bit integers corresponding to the line plot colors.
        ;
        ; NPLOTCOLORS = Returns the number of line plot colors defined.
        ;
        ; TABLESIZE = Returns the number of color table indices.
        ;
        ; KEYWORDS:
        ; DECOMPOSED = Set this keyword to explicitly use decomposed color
        ; on 24-bit machines. Has no effect on devices which
        ; do not support decomposed color. Set this keyword
        ; to 0 to turn off decomposed color on 24-bit devices.
        ;
        ; /SYSTEM_VARIABLES: Define system variables with the name of each
        ; color and the value of the color table index
        ; or the 24-bit integer corresponding to each
        ; color, i.e. for 24-bit color, !orange=32767L.
        ; This is very useful since system variables have
        ; global scope, therefore these colors can be
        ; used in any procedure once defined.
        ;
        ; /GETINFO: Do not do anything to the color table, just print
        ; out IDL color information.
        ;
        ; /SILENT: Do not print out IDL color information. Default is to
        ; print info.
        ;
        ; /TEST: Display the entire color table and the names of
        ; the line plot colors in their respective colors.
        ;
        ; /START: Put the line plot colors at the start of the color
        ; table. Default is to store them at the top.
        ;
        ; /NOCOLORS: Do not load line plot colors into color table!
        ; Has no effect if color undecomposed.
        ;
        ; /PSEUDO256: Default is to establish PseudoColor visual using
        ; only the available color indices when the first
        ; window is created. This keyword forces IDL to
        ; use all 256 colors.
        ;
        ; COMMON BLOCKS:
        ; COLORS: The IDL color common block.
        ;
        ; SIDE EFFECTS:
        ; The color table may be modified. If a window is not open, a
        ; pixmap is created then destroyed to establish the visual class
        ; and depth. If the /TEST keyword is set and the device is X
        ; Windows, a free window is created to display the color table
        ; and line plot colors.
        ;
        ; RESTRICTIONS:
        ; Only supported by IDL v5.2 or higher.
        ;
        ; PROCEDURES CALLED:
        ; STRETCH
        ;
        ; EXAMPLE:
        ; To view the color table and line plot names and colors:
        ;
        ; IDL> setcolors, /test
        ;
        ;
        ; To define system variables with the names of each color
        ; and values of the corresponding color table index or 24-bit
        ; long integer:
        ;
        ; IDL> setcolors, /SYSTEM_VARIABLES
        ;
        ;
        ; To use the line plot colors (set DECOMPOSED=1 if 24-bit display):
        ;
        ; IDL> setcolors, NAMES=cnames, VALUES=cindx
        ; IDL> plot, findgen(30), co=cindx[(where(cnames eq 'yellow'))[0]]
        ; OR
        ; IDL> plot, findgen(30), co=getcolor('yellow',cnames,cindx)
        ;
        ;
        ; If you'd like to display an image but you've added line plot
        ; colors to the color table, you need to scale the image to
        ; avoid using the plotcolors:
        ;
        ; IDL> setcolors, NPLOTCOLORS=nplotcolors, TABLESIZE=tablesize
        ; IDL> tv, bytscl(image, top=tablesize-nplotcolors-1)
        ; If you load the line plot colors at the start of the color table:
        ;
        ; IDL> setcolors, NPLOTCOLORS=nplotcolors, TABLESIZE=tablesize, /START
        ; IDL> tv, bytscl(image, top=tablesize-nplotcolors-1)+nplotcolors
        ;
        ; (Do not use TVSCL! "If color is important to you (and it almost
        ; always is), then you probably never want to use the TVScl command.
        ; Instead, you will want to scale your image data yourself, and use
        ; the TV command to display it." - David W. Fanning)
        ;
        ;
        ; To load your own line plot colors:
        ;
        ; IDL> setcolors, PLOTCOLORS=['red','yellow','blue','green'], $
        ; IDL> R_PLOT=[255,255,0,0], G_PLOT=[0,255,0,255], $
        ; IDL> B_PLOT=[0,0,255,0], NAMES=cnames, VALUES=cindx
        ;
        ; (Color 'WHITE' will be appended to the top of the color table
        ; to protect !p.color/!p.background. If /START is set, color
        ; 'BLACK' is appended to bottom of color table.)
        ;
        ;
        ; If you want to make a grayscale image and add colored
        ; annotation (when color decomposition is off):
        ;
        ; IDL> setcolors, NPLOTCOLORS=nplotcolors, TABLESIZE=tablesize, $
        ; IDL> NAMES=cnames, VALUES=cindx
        ; IDL> tv, bytscl(image, top=tablesize-nplotcolors-1)
        ; IDL> xyouts, 200, 150, 'M31', /dev, $
        ; IDL> co=cindx[(where(cnames eq 'cyan'))[0]]
        ; OR
        ; IDL> xyouts, 200, 150, 'M31', /dev, co=getcolor('cyan',cnames,cindx)
        ;
        ; WARNING! After opening a PostScript file you should run
        ; SETCOLORS! If you're using a 24-bit visual device,
        ; the system variables and color indices will be 24-bit longword
        ; integers (with values greater than 256) but PostScript is an
        ; 8-bit device with only 256 colors available, so right after opening
        ; a PostScript file, you should run SETCOLORS to re-establish the
        ; color system variables color indices. Likewise, when you close
        ; a PostScript image, you should run SETCOLORS again in order to
        ; re-establish the colors for X Windows.
        ;
        ; NOTES:
        ; Once a window is open, the visual class is established for the IDL
        ; session. There is no way to change it once it is established.
        ; However, if no window is open (there's no way to tell if one has
        ; been opened in the past) we open a pixmap and delete it just to
        ; establish the visual class and depth.
        ;
        ; I thought at first it would be convenient to store the color table
        ; indices of each color in a variable named after the corresponding
        ; color and storing each color variable in a common block. However, I
        ; was convinced by two very bright folks that common blocks should be
        ; avoided, especially for this use.
        ;
        ; RELATED PROCEDURES:
        ; GETCOLOR
        ;
        ; MODIFICATION HISTORY:
        ; Written by Tim Robishaw, Berkeley 13 Aug 2001
        ; Added /NOCOLORS keyword. TR, Berkeley 03 Oct 2001
        ; Added /SYSTEM_VARIABLES keyword. TR, 07 Feb 2002
        ; Added /PSEUDO256 keyword. TR, 15 Feb 2002
        ; Changed to gsetcolors to work with gdl, but will not work with
        ; any grayscale or B&W devices, gives wrong visual type, Bruce
        ; Grossan Sept. 2014
        ;-

        on_error, 2

        ; FIND IDL VERSION NUMBER... 5.2 OR HIGHER...
        if (float(!version.release) lt 5.2) then begin
        message,'This routine is only supported on IDL version 5.2 or higher',/INFO
        return
        endif

        ; IF NOT IN X WINDOWS, DECOMPOSED DOESN'T MEAN ANYTHING!
        if (!d.name eq 'X') then begin

        ; SET COLOR DECOMPOSITION EXPLICITLY?
        if (N_elements(DECOMPOSED) gt 0) then device, DECOMPOSED=decomposed
        
        ; A WINDOW NEEDS TO HAVE BEEN CREATED TO ESTABLISH THE VISUAL TYPE...
        if (!d.window eq -1) then begin
            window, /FREE, /PIXMAP, COLORS=256*keyword_set(PSEUDO256)
            wdelete, !d.window
        endif
        
        ; WHAT VISUAL STATES HAVE BEEN SET?
        

        ; device, get_visual_name=visual, $ ; doesn't work in GDL
        device, $
        get_visual_depth=depth, $
        get_decomposed=decomposed
        visual='standardXterm' ; another hack for gdl

        ; CAN'T DISPLAY COLORS IF WE HAVE A GRAYSCALE VISUAL...
        

        ; if (strupcase(visual) eq 'GRAYSCALE') OR $
        ; (strupcase(visual) eq 'STATICGRAY') then begin
        ; message, 'Cannot set colors with '+strtrim(visual,2)+' visual!', /INFO
        ; if keyword_set(SILENT) $
        ; then return $
        ; else goto, output
        ; endif

        endif else decomposed=0

        size = !d.table_size ; WHAT IS THE COLOR TABLE SIZE?
        ncol = !d.n_colors ; HOW MANY COLORS ARE AVAILABLE?

        ; DO YOU JUST WANT THE CURRENT VISUAL INFO...
        if keyword_set(GETINFO) then goto, output

        ; THE IDL-DEFINED COLOR COMMON BLOCK...
        common colors, r_orig, g_orig, b_orig, r_curr, g_curr, b_curr

        ; LOAD THE ORIGINAL COLOR TABLE...
        if (N_elements(r_orig) eq 0) then begin
        r_orig = bytscl(bindgen(size))
        g_orig = r_orig
        b_orig = r_orig
        endif
        tvlct, r_orig, g_orig, b_orig

        ; DO WE USE PREDEFINED PLOTCOLORS OR USER-SPECIFIED...
        if (N_elements(PLOTCOLORS) eq 0) then begin

        ; DO WE NOT WANT TO ADD LINE PLOT COLORS...
        if decomposed or (not decomposed AND not keyword_set(NOCOLORS)) then begin

        ; NAMES OF THE PLOTCOLORS...
        names = [ 'black',  $
                  'red',    $
                  'orange', $
                  'green',  $
                  'forest', $
                  'yellow', $
                  'cyan',   $
                  'blue',   $
                  'magenta',$
                  'purple', $
                  'gray',   $
                  'white']
        
        ; GENERATE RGB COLORS FOR COLORED LINE PLOTS...
        ;              k  r   o  g   f  y  c  b  m   p   g  w
        r_plot = 255b*[0, 1,  1, 0,  0, 1, 0, 0, 1,  0,  0, 1]$
                +byte([0, 0,  0, 0, 35, 0, 0, 0, 0,153,127, 0])
        g_plot = 255b*[0, 0,  0, 1,  0, 1, 1, 0, 0,  0,  0, 1]$
                +byte([0, 0,127, 0,142, 0, 0, 0, 0, 50,127, 0])
        b_plot = 255b*[0, 0,  0, 0,  0, 0, 1, 1, 1,  0,  0, 1]$
                +byte([0, 0,  0, 0, 35, 0, 0, 0, 0,205,127, 0])
        

        endif

        endif else begin

        ; ONLY NEEDS TO BE DONE IF UNDECOMPOSED!!!!!
        ; COLORS PROTECTED OTHERWISE!!!
        
        ; MAKE SURE RIGHT # OF RGB & NAMES...
        if (N_elements(R_PLOT)+N_elements(G_PLOT)+N_elements(B_PLOT))/3. $
          ne N_elements(PLOTCOLORS) then $
          message, 'PLOTCOLORS, R_PLOT, G_PLOT, & B_PLOT must have same size!'
        
        ; PLOTCOLORS HAD BETTER BE A STRING ARRAY...
        if (size(PLOTCOLORS,/TNAME) ne 'STRING') then $
          message, 'PLOTCOLORS must be of type STRING!'
        
        ; IF YOU'RE SILLY AND PUT MORE THAN ONE VALUE OF A COLOR IN
        ; THE TABLE... OH WELL, YOUR PROBLEM...
        if not keyword_set(START) then begin
        
            ; FORCE COLOR 'WHITE' TO BE AT TOP OF COLOR TABLE...
        

        ; good = where(strupcase(plotcolors) ne 'WHITE', ngood) ; no
        ; strupcase in gdl
        good = where( (plotcolors ne 'WHITE') and (plotcolors ne 'white'), ngood)

            if (ngood ne 0) then begin
                plotcolors = plotcolors[good]
                names  = [plotcolors,'white']
                r_plot = [r_plot[good],size-1]
                g_plot = [g_plot[good],size-1]
                b_plot = [b_plot[good],size-1]
            endif else names = plotcolors
        
        endif else begin
        
            ; FORCE COLOR 'BLACK' TO BE AT BOTTOM OF COLOR TABLE...
            good = where(strupcase(plotcolors) ne 'BLACK', ngood)
            if (ngood ne 0) then begin
                plotcolors = plotcolors[good]
                names  = ['black',plotcolors]
                r_plot = [234,r_plot[good]]
                g_plot = [123,g_plot[good]]
                b_plot = [211,b_plot[good]]
            endif else names = plotcolors
        
        endelse
        

        endelse

        ; HOW MANY PLOTCOLORS HAVE WE CREATED?
        nplotcol = N_elements(names)

        ; DO YOU EVEN HAVE THIS MANY COLORS AVAILABLE???
        ; AS CRAZY AS IT SOUNDS, THIS HAS HAPPENED!
        if (ncol le nplotcol) then begin
        message, 'Close some windows! Not enough available colors!', /info
        return
        endif

        if not decomposed then begin
        ; WE HAVE AN 8-BIT DISPLAY, OR 24-BIT WITH COLOR DECOMPOSITION OFF

        ; STRETCH THE CURRENT COLOR TABLE OVER THE RANGE THAT 
        ; WON'T BE USED BY OUR PLOT COLORS...
        ; THE CURRENT COLOR TABLE IS STORED IN "ORIG" COLOR VECTORS.
        ; AFTER THE STRETCH, THE "CURR" COLOR VECTORS WILL CONTAIN
        ; THE NEW COLOR TABLE...
        if not keyword_set(START) then begin
            start = size-nplotcol
            stretch, 0, start-1
        endif else begin 
            start = 0
            stretch, nplotcol, size-1 
        endelse
        
        ; IF WE WANT PLOT COLORS, ADD THEM TO COLOR TABLE...
        if not keyword_set(NOCOLORS) then begin
            ; THE COLOR TABLE INDICES OF THE LINE PLOT COLORS...
            ctindx = bindgen(nplotcol)+byte(start)
        
            ; STORE THEM IN THE SPECIFIED ROWS OF THE NEW COLOR TABLE...
            r_curr[ctindx] = r_plot
            g_curr[ctindx] = g_plot 
            b_curr[ctindx] = b_plot
        
            ; LOAD THE NEW COLOR TABLE...
            tvlct, r_curr, g_curr, b_curr
        endif
        
        ; WE WANT TO LEAVE THE "ORIG" VALUES AS THEY WERE WHEN SENT IN!
        ; IF THEY WERE SET TO "CURR" VALUES NOW, IF THIS ROUTINE WERE CALLED
        ; AGAIN, THE PLOTCOLORS WOULD BE STRETCHED INTO THE COLOR TABLE!
        

        endif $
        ; OTHERWISE WE HAVE A 24-BIT DISPLAY...
        else ctindx = long(r_plot) + ishft(long(g_plot),8) + ishft(long(b_plot),16)

        ; SET THESE COLOR NAMES AS SYSTEM VARIABLES...
        if keyword_set(SYSTEM_VARIABLES) then $
        for i = 0, N_elements(names)-1 do begin
        success = execute('defsysv, "!'+names[i]+'", long(ctindx[i]), 0')
        if not(success) $
        ; then message, '!'+strupcase(names[i])+' not changed.', /cont
        then message, '!'+names[i]+' not changed.', /cont
        endfor

        ; DISPLAY THE COLOR TABLE AND SEE IF THE COLORS ARE CORRECT...
        if keyword_set(TEST) then begin
        if (!d.name eq 'X') then begin
        window, /FREE, /PIXMAP
        wn = !d.window & wdelete, wn
        window, /FREE, YSIZE=2*size, XSIZE=size, $
        TITLE='IDL '+strtrim(wn,2)+': Plot Colors'
        endif
        if (!d.name eq 'PS') then $
        device, xsize=3, ysize=6, xoff=(8.5-3)/2., yoff=(11.-6)/2., /inches
        device, set_font='Helvetica Bold', /tt_font
        tv, matrix_multiply(intarr(size)+1,[indgen(size),indgen(size)])
        prefix = keyword_set(SYSTEM_VARIABLES) ? '!!' : ''
        for i = 0.0, nplotcol-1.0 do begin
        printcolor = 'xyouts, 0.45, '+strtrim((i+1)/(nplotcol+1),2)$
        +', '''+prefix+names[i]+''', font=1, /norm, charsize=2.0, co='$
        +strtrim(long(ctindx[i]),2)
        useless = execute(printcolor)
        endfor
        endif

        ; OUTPUT THE COLOR TABLE INFO...
        output:
        if not keyword_set(SILENT) OR keyword_set(GETINFO) then begin
        print, 'Display Device : ', !d.name, format='(%"\N",2A)'
        if (!d.name eq 'X') then begin
        print, 'Visual Class : ', visual
        print, 'Visual Depth : ', strtrim(depth,2)+'-Bit'
        endif
        print, 'Color Table Size: ', strtrim(!d.table_size,2)
        print, 'Number of Colors: ', strtrim(!d.n_colors,2)
        print, 'Decomposed Color: ', strtrim(decomposed,2), format='(2A,%"\N")'
        endif

        end; setcolors

         
      • giloo

        giloo - 2014-09-06

        testsuite/test_widgets should work if wxWidgets was linked with gdl. Does it?

         
        • cosmicbruce

          cosmicbruce - 2014-09-08

          Due to the next comment about updating the CVS, I did:

          sudo port upgrade --enforce-variants gnudatalanguage +wxWidgets

          I then compiled the test suite, then ran widget2. It returned the error " GDL was compiled without support for wxWidgets". So, somehow, I am not getting the option.

          Thanks,

          -Bruce

           
  • giloo

    giloo - 2014-09-06

    hi,
    I've just updated the CVS --- GDL will silently discard a few font-related keywords that were preventing to use these procedures "as such".

    setcolors,/test and your 2 examples work.
    You have to do setcolor,/system to be able to use '!green" etc values.

     
  • cosmicbruce

    cosmicbruce - 2014-09-08

    HI again "giloo".

    After a macports upgrade, this works for X windows, but definitely not for the PS device.

    GDL>set_plot,'ps'
    GDL> setcolors,/system
    GDL> plot,[9,6,8]
    GDL> oplot,[9,6,8]+1,psym=6,color=!green
    GDL> device,/close

    No green. Any suggestions?

    Thanks,

    -Bruce

     
  • giloo

    giloo - 2014-09-10

    hi,
    just define the ps as color output:
    device,/color
    before plotting.
    As IDL would do.

     
    • cosmicbruce

      cosmicbruce - 2014-09-10

      Aha! Found the problem: No default black in PS - perhaps a bug?

      This does NOT work:

      GDL> set_plot,'ps'
      GDL> device,/color
      GDL> plot,[9,4,8] & oplot,[9,4,8]-1,color=!red,psym=4
      GDL> device,/close

      All you get are some cutoff symbols.

      This DOES work correctly:

      GDL> set_plot,'ps'
      GDL> device,/color
      GDL> plot,[9,4,8],color=!black & oplot,[9,4,8]-1,color=!red,psym=4
      GDL> device,/close

      You get the plot window and line in black and the symbols in red.

      -CB

       
  • giloo

    giloo - 2014-09-10

    I note that IDL8 knows about a !COLOR structure with dozens of colors (web w3c colors). This should be implemented in gdl, so one would not need setcolors in general.

     
  • giloo

    giloo - 2014-09-11

    Hi,
    I'm not sure you have the cutting-edge GDL version of the SF CVS repository---Is it really as simple as a macports upgrade?
    On the CVS the color handling has been largely modified recently. I'm pleased that the behaviour of your demo is the same between IDL and GDL for this new version.

    The trick is that !red is not the same if you use setcolors,/system BEFORE or AFTER defining set_plot,'ps'...

     
  • cosmicbruce

    cosmicbruce - 2014-09-12

    I have a couple more comments:

    1. re: version: GDL - GNU Data Language, Version 0.9.4
      I really don't know what one has to do to get code from the CVS to macports. Anyway, it is beyond my abilities to install/compile without macports.

    2. re: ps still doesn't work. Here is my careful example:

    GDL> device,/close
    GDL> set_plot,'ps'
    GDL> device,/color
    GDL> setcolors,/system
    Display Device : PS
    Color Table Size: 256
    Number of Colors: 256
    Decomposed Color: 0
    GDL> plot,[3,2,9],psym=4,symsize=3 & oplot,[3,2,9]-.5,color=!blue, symsize=3,psym=1
    GDL> device,/close
    .. and plot frame is still white on white.

    One STILL has to use plot keyword color=!black as the default color AND background are white in PS.

    1. Curiously, when I start up gdl from scratch, I still have color system variables, e.g. !green, !magenta. Not sure if that means the version I have is now default, or…?

    Thanks very much for your help and response.

    -Bruce

     
  • giloo

    giloo - 2014-09-12

    yes, all the improvements I refer to are only in the CVS. The 0.9.4 version is one year old and its color support in PS is buggy. At least you have found a way to get PS file that are OK.

    A new version 0.9.5 should appear soon, and compilation from day-to-day CVS content on Mac is also possible, see e.g. http://gdl.referata.com/wiki/Compiling_(Mac)

    I can see no way gdl-0.9.4 can know of !green from scratch unless this system variable has been defined somehow in an eventual startup file ($IDL_STARTUP)

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks