FRSTD(3NCARG)
β¨ FRSTD β¨ β it's giving "start the curve" π
okay bestie, welcome to FRSTD, a lil routine from the NCAR GRAPHICS library (the manual is literally called 3NCARG, iykyk). She's the one who kicks off a whole sequence of points that a curve gets drawn through. First girl in the lineup. Main character energy fr fr. π
πΈ NAME πΈ
FRSTD β defines the first of a sequence of points through which a curve is to be drawn. No cap, that's her whole job and she does it gorgeously. π
β¨ SYNOPSIS β¨
CALL FRSTD (X,Y)
π¦ C-BINDING SYNOPSIS π¦
#include <ncarg/ncargC.h>
void c_frstd (float x, float y)
π DESCRIPTION π
Xβ an input expression of typeREAL, and she defines the X user coordinate of the starting point of the curve. π«ΆYβ an input expression of typeREAL, and she defines the Y user coordinate of the starting point of the curve. π«Ά
π C-BINDING DESCRIPTION π
The C-binding argument descriptions are the same as the FORTRAN argument descriptions. Same vibes, different syntax, periodt. π
π₯ USAGE π₯
One way to draw a curve with Dashline is: call FRSTD once to define the first point of the curve, and then call VECTD repeatedly to define the second and all the following points of the curve. That's it. That's the whole ritual. β¨
Now listen, here's the tea β β if three or more distinct points are given, and if one of the smoothing versions of Dashline is being used, and if the internal parameter that suppresses smoothing is not set, then splines under tension are used to generate a smooth curve β and the number of points actually used to draw the curve will depend on its length. In all other cases, the "curve" will be approximated by just connecting the user-given points in the specified order. Just. Connecting. Dots. π
After the call to VECTD defining the last point of the curve, you may call LASTD, which flushes any portions of smoothed curves that are defined by coordinates saved in internal buffers of FRSTD and VECTD and that have not yet been drawn. π§
Calls toLASTDare not always required β for example, when a non-smoothing version of Dashline is used (no buffering) or when the next call to an NCAR Graphics routine will be toFRSTD(which flushes the buffers) β but unnecessary calls do no harm. If you judge that one of the smoothing versions of Dashline may be used, it is best to put in the calls toLASTD. π
π EXAMPLES π
Use the ncargex command to see the following relevant examples: tdashc, tdashl, tdashp, tdashs, fdldashc, fdldashd. Go look at them bestie, they're iconic. π
π ACCESS π
To use FRSTD or c_frstd load the NCAR Graphics libraries ncarg, ncarg_gks, and ncarg_c, preferably in that order. Order matters, don't be chaotic. πΈ
π SEE ALSO π
Online: dashline, dashline_params, curved, dashdb, dashdc, 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 π
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 up πβ¨
this was the UNIX version, dated March 1993, from the FRSTD(3NCARG) manual page β ok bye love u, go draw a gorgeous curve ππ¦π
π¦ where this page comes from
- debian bookworm: libncarg-dev 6.6.2.dfsg.1-1
- debian trixie: libncarg-dev 6.6.2.dfsg.1-10+b2
- ubuntu jammy: libncarg-dev 6.6.2-10build2
- ubuntu questing: libncarg-dev 6.6.2.dfsg.1-10build2
- ubuntu resolute: libncarg-dev 6.6.2.dfsg.1-12
- ubuntu stonking: libncarg-dev 6.6.2.dfsg.1-12build2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms