DASHDC(3NCARG)

πŸ’… DASHDC β€” it's in the NCAR GRAPHICS fam, bestie

okay so this is the DASHDC page from NCAR GRAPHICS, and it's literally about drawing dashed lines with cute little labels on them. It defines a dash pattern with labels. But heads up: if DASHDC gets called while the "quick" version of Dashline is the one in use, you get an error exit. No cap. πŸ’€


✨ SYNOPSIS ✨

CALL DASHDC (IPAT,JCRT,JSIZE)

🌈 C-BINDING SYNOPSIS 🌈

#include <ncarg/ncargC.h>

void c_dashdc (char *ipat, int jcrt, int jsize)

πŸŽ€ DESCRIPTION πŸŽ€

  • IPAT β€” this is an input constant or variable of type CHARACTER, and it's the one that says what dash pattern we're using, periodt. Like, IPAT can technically be any length you want, but ngl, 60 characters is kinda the practical limit. This pattern just keeps repeating for successive line segments until the whole entire line is drawn. Here's the tea on the characters:
    • a dollar sign in IPAT means solid πŸ’–
    • an apostrophe means a gap πŸ•³οΈ
    • blanks? ignored, they're not the main character
    • any character in IPAT that isn't a dollar sign, apostrophe, or blank is considered part of a line label. Each line label can be at most 15 characters long, so don't go overboard. Sufficient white space gets reserved in the dashed line for writing those line labels, so they have room to breathe. ✨
  • JCRT β€” an input expression of type INTEGER, and it specifies that the length assigned to each increment of the line pattern is (JCRT/1023.) NDCs (Normalized Device Coordinates, iykyk). Each increment is either a gap β€” that's the dollar sign in IPAT β€” or a line segment, which is the apostrophe in IPAT. JCRT has to be greater than or equal to 1, so like, be so serious about that.
  • JSIZE β€” an input expression of type INTEGER, and it specifies the width of the plotted characters. It goes like this:
    • 0 β†’ .0078 NDCs
    • 1 β†’ .0117 NDCs
    • 2 β†’ .0156 NDCs
    • 3 β†’ .0234 NDCs
    • >3 β†’ JSIZE/1023. NDCs

πŸ¦‹ C-BINDING DESCRIPTION πŸ¦‹

The C-binding argument descriptions are literally the same as the FORTRAN argument descriptions. Same energy, different language, we love a consistent icon. πŸ’…


πŸ”₯ EXAMPLES πŸ”₯

Use the ncargex command to see the following relevant examples: tdashc, tdashp, tdashs, fcoord1, fcoord2, fdldashc, fdldashd. Go look at them, they ate. πŸ‘‘


🌸 USAGE 🌸

DASHDC may be called to define a dash pattern for any of the four versions of Dashline β€” except the "quick" version. If you call it while the "quick" version is in use, an error exit will result. So like, read the room, check which version you're running first. 😭

A dash pattern defined by a call to DASHDC will supersede one defined by an earlier call to DASHDB or DASHDC. Newer pattern wins, that's just the rules. ✨


πŸ‘‘ ACCESS πŸ‘‘

To use DASHDC or c_dashdc, load the NCAR Graphics libraries ncarg, ncarg_gks, and ncarg_c β€” preferably in that order. Order matters, bestie, don't fight it. 🫢


πŸ’œ SEE ALSO πŸ’œ

  • Online: dashline, dashline_params, curved, dashdb, frstd, lastd, lined, reset, vectd, ncarg_cbind
  • Hardcopy: NCAR Graphics Contouring and Mapping Tutorial; NCAR Graphics Fundamentals, UNIX Version; User's Guide for NCAR GKS-0A Graphics

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, babe πŸ’– this was DASHDC(3NCARG) from the UNIX manual, dated March 1993, and it lives in the NCAR GRAPHICS collection. mwah, go draw some dashed lines with labels, you've got this πŸŽ€βœ¨