VECTD(3NCARG)

✨ VECTD ✨ (from the NCAR Graphics manual, bestie)

okay so this is the page for VECTD — a little Fortran routine from NCAR GRAPHICS that adds the next point to a curve you're drawing 💖

---

🎀 NAME 🎀

VECTD — defines the second and following points of a sequence of points that a curve gets drawn through. (First one's somebody else's job, we'll get to that 👀)

---

🦋 SYNOPSIS 🦋

CALL VECTD (X,Y)

---

💅 C-BINDING SYNOPSIS 💅

#include <ncarg/ncargC.h>

void c_vectd (float x, float y)

---

🌸 DESCRIPTION 🌸

• X — an input expression of type REAL. It's the X user coordinate of the next point in your sequence of points defining a curve. 💫
• Y — an input expression of type REAL. It's the Y user coordinate of the next point in that same sequence. Periodt.

---

🌈 C-BINDING DESCRIPTION 🌈

The C-binding argument descriptions are literally the same as the FORTRAN argument descriptions. Same vibes, different language, no notes. 🫶

---

👑 USAGE 👑

One way to draw a curve with Dashline: call FRSTD once to define the first point of the curve, then call VECTD over and over to define the second point and every point after that. That's the whole routine, no cap. ✨

So here's the tea on smoothing ☕:

• If you give three or more distinct points, and one of the smoothing versions of Dashline is being used, and the internal parameter that suppresses smoothing is not set — then splines under tension are used to generate a smooth curve. The number of points actually used to draw the curve depends on its length. 🌊
• In all other cases, the "curve" is just approximated by connecting the user-given points in the specified order. Straight-up connect-the-dots, iconic behaviour honestly. 🔥

After the call to VECTD that defines 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 to LASTD are 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 to FRSTD (which flushes the buffers). But unnecessary calls do no harm. So if you judge that one of the smoothing versions of Dashline may be used, it's best to put in the calls to LASTD. Better safe than sorry, bestie. 🙈

---

🍓 EXAMPLES 🍓

Use the ncargex command to see these relevant examples: tdashc, tdashl, tdashp, tdashs, fdldashc, fdldashd. Go look at them, they ate. 💜

---

⭐ ACCESS ⭐

To use VECTD or c_vectd, load the NCAR Graphics libraries ncarg, ncarg_gks, and ncarg_c — preferably in that order. Order matters, don't fight it. 💅

---

🧚 SEE ALSO 🧚

Online: dashline, dashline_params, curved, dashdb, dashdc, frstd, lastd, lined, reset, 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 🎀 this one's from the UNIX manual, dated March 1993, source/version VECTD(3NCARG) — go forth and plot, main character 💅✨