VECT3(3NCARG)

💅 VECT3 — bestie's guide to drawing the rest of the line ✨

NCAR GRAPHICS · 3NCARG · the one where you keep the pen moving 🖊️

---

🌸 NAME 🌸

VECT3</purl> — defines the second and all subsequent points in a sequence of points connected by straight-line segments, the projections of which are to be drawn. (FRST3 is called for the first point in the sequence and VECT3 is called for the rest.) Like, FRST3 starts the story and VECT3 writes the rest of the chapters, no cap. 📖

---

✨ SYNOPSIS ✨

CALL VECT3 (U,V,W)

---

🦋 C-BINDING SYNOPSIS 🦋

#include <ncarg/ncargC.h>

void c_vect3 (float u, float v, float w)

---

💖 DESCRIPTION 💖

• U,V,W — input expressions of type REAL, and they're the coordinates of a point in 3-space to the projection of which a line is to be drawn. Three whole dimensions, bestie, we're living in 3D. 🧊✨

So here's the tea: every single call to FRST3 moves a conceptual "pen" 🖊️ to the new starting point for a sequence of line draws. Then every call to VECT3 draws a line from the current pen position to a new pen position, and then makes that new spot the current pen position. It's giving "pen walks forward and never looks back." 🚶♀️💨

Line segments are drawn in the current polyline color, as determined by the last call to the GKS routine GSPLCI; by default, color index 1 is used. Line width is determined by the last call to the GKS routine GSLWSC; by default, the value of the line width scale factor is 1. So yes, the vibes of your line are entirely in the hands of whoever you called last. 👑

⚠️ Okay this part is IMPORTANT and I need you to actually read it, bestie: the routines FRST3 and VECT3 do NOT flush the SPPS pen-move buffer. In fact, to have them do so would entirely defeat the purpose of that buffer. So if your last call was to the routine VECT3 and you are about to call GKS routines to change color or line width, you must first call the SPPS routine PLOTIF to flush the buffer; otherwise, the color and line width changes will affect line draws flushed from the buffer later. 😭 Like, the buffer is holding your old settings hostage. Free them with PLOTIF. Periodt. 💅

---

🎀 C-BINDING DESCRIPTION 🎀

The C-binding argument descriptions are the same as the FORTRAN argument descriptions. Same energy, different syntax, we love consistency. 🫶

---

🌈 EXAMPLES 🌈

Use the ncargex command to see the following relevant examples: fthex01, fthex02, fthex03. Go look at them, they ate. 🔥

---

👑 ACCESS 👑

To use VECT3 or c_vect3, load the NCAR Graphics libraries ncarg, ncarg_gks, and ncarg_c, preferably in that order. Order matters, don't do your own thing here. 🧚

---

💜 SEE ALSO 💜

Online: threed, curve3, fence3, frst3, line3, perim3, point3, psym3, pwrz, pwrzt, set3, threed, tick3, tick43, ncarg_cbind.

(yes threed is listed twice, I don't make the rules, I just report them 💀)

Hardcopy: NCAR Graphics Fundamentals, UNIX Version

---

🌸 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 iconic little manual page comes from the UNIX manual, March 1993 edition, filed under VECT3(3NCARG) — mwah, no notes. 💋🦋