GSET_COLR_REP(3NCARG)

πŸ“¦ version 6.6.2, in epel 9, fedora 43, fedora 44

πŸ’– GSET_COLR_REP (3NCARG) πŸ’–

okay bestie, so this is a page from NCAR Graphics (the 3NCARG manual, you know the vibe) and it's all about gset_colr_rep β€” aka Set color representation β€” which is literally just the glow-up moment where a color value gets matched up with a color index. πŸ’…


✨ NAME ✨

gset_colr_rep (Set color representation) β€” associates a color value with a color index. that's it, that's the whole job, and she does it gorgeously πŸŽ€


🌸 SYNOPSIS 🌸

#include <ncarg/gks.h>

void gset_colr_rep(Gint ws_id, Gint colr_ind, const Gcolr_rep
*colr_rep);

πŸ¦‹ DESCRIPTION πŸ¦‹

here's the tea on every single argument, no skipping, we don't do that here:

  • ws_id β€” (Input) a workstation identifier. and listen, ws_id must be the same one you used in some previous gopen_ws call. like, she needs to already know you. no cold intros allowed 🫢
  • colr_ind β€” (Input) a color index. just the number, bestie.
  • colr_rep.rgb.red β€” (Gfloat, Input) an intensity value for red, between 0. and 1. inclusive.
  • colr_rep.rgb.green β€” (Gfloat, Input) an intensity value for green, between 0. and 1. inclusive.
  • colr_rep.rgb.blue β€” (Gfloat, Input) an intensity value for blue, between 0. and 1. inclusive.

three floats, all of them living between 0. and 1. inclusive. that's the range, respect it πŸ’œ


πŸ”₯ USAGE πŸ”₯

okay so, color in GKS is "indexed". meaning: color attributes get assigned to primitives by using a color index. and the GKS function gset_colr_rep is the one you call to associate a color value with color indices. she's the matchmaker fr fr πŸ’–

it is recommended that all color indices used in a given job be defined prior to calling any output primitive. and because the result of a dynamic color change can be ambiguous, it is also recommended that gset_colr_rep not be called to change a color value after the original definitions. define her once, define her right, and let her live. πŸ™ˆ

gset_colr_rep may be called after opening the workstation for which the color indices are to be defined, and not before that workstation is opened. read that again. it's giving "you must be seated before you order" energy.

different color tables can be maintained for different workstations β€” which is iconic actually. for example, color index 2 for a CGM file may be associated with "red" while at the same time it may be associated with "green" for some X workstation. same index, different girl, different workstation, no drama. 🌈

⚠️ it is important to stress that color index 0 defines the background color. if any color indices are defined, then you should define the background color index 0. otherwise you run the risk of having a user-defined color match the default background color. that's the jumpscare. define index 0, bestie. please. 😭

for all GKS output primitives, color is assigned by an indexing scheme. the indices run from 0 to 255, where 0 is the background color index and 1 is the foreground color index. πŸ‘‘


πŸ‘‘ ACCESS πŸ‘‘

to use the GKS C-binding routines, load the ncarg_gks and ncarg_c libraries. both. not one. both. ✨


🌟 SEE ALSO 🌟

Online:

  • ginq_colr_rep(3NCARG)
  • gset_line_colr_ind(3NCARG)
  • gset_marker_colr_ind(3NCARG)
  • gset_fill_colr_ind(3NCARG)
  • gset_text_colr_ind(3NCARG)
  • ginq_line_colr_ind(3NCARG)
  • ginq_marker_colr_ind(3NCARG)
  • ginq_fill_colr_ind(3NCARG)
  • ginq_text_colr_ind(3NCARG)
  • gks(3NCARG)
  • ncarg_gks_cbind(3NCARG)

Hardcopy: User's Guide for NCAR GKS-0A Graphics; NCAR Graphics Fundamentals, UNIX Version


Copyright (C) 1987-2009 University Corporation for Atmospheric Research

The use of this Software is governed by a License Agreement.


and that's the whole page, bestie, you ate it πŸ’… this one came from the UNIX manual, March 1993, filed under GSET_COLR_REP(3NCARG) β€” vintage, but she still slays πŸŽ€βœ¨

πŸ“¦ where this page comes from