QwtCPointerData(3)

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

✨ NAME ✨

QwtCPointerData β€” that's it bestie, that's the whole name, she's giving minimalism, she's giving mystery πŸ’…


🌸 SYNOPSIS 🌸

#include <qwt_data.h>

Inherits QwtData. No cap. πŸ’–

🫢 Public Member Functions 🫢

  • QwtCPointerData (const double *x, const double *y, size_t size)
  • virtual QwtDoubleRect boundingRect () const
  • virtual QwtData * copy () const
  • QwtCPointerData & operator= (const QwtCPointerData &)
  • virtual size_t size () const
  • virtual double x (size_t i) const
  • const double * xData () const
  • virtual double y (size_t i) const
  • const double * yData () const

πŸ¦‹ Additional Inherited Members πŸ¦‹

There's more stuff that comes along for the ride from QwtData β€” this page literally just says Additional Inherited Members and then dips πŸ™ˆ so that's all the tea we're getting here.


πŸ“– Detailed Description πŸ“–

OK so picture this: it's a data class that holds two pointers to memory blocks of doubles. That's the whole vibe. Two pointers, one job, main character energy πŸ”₯


πŸ› οΈ Constructor & Destructor Documentation πŸ› οΈ

QwtCPointerData::QwtCPointerData (const double *x, const double *y, size_t size)

Constructor ✨ β€” she's the one who makes the object exist, iconic behaviour honestly.

Parameters:

  • x β€” array of x values 🌸
  • y β€” array of y values 🌸
  • size β€” size of the x and y arrays πŸ“
⚠️ Warning, and I need you to actually hear me on this one bestie: the programmer must assure that the memory blocks referenced by the pointers remain valid during the lifetime of the QwtPlotCPointer object. Like, the pointers do NOT own that memory. If it goes away while your object is still alive, that's a you problem and it will be a bad time πŸ’€

See also: QwtPlotCurve::setData(), QwtPlotCurve::setRawData() πŸ‘‘


πŸ”§ Member Function Documentation πŸ”§

QwtDoubleRect QwtCPointerData::boundingRect () const [virtual]

Returns the bounding rectangle of the data. And if there's no bounding rect β€” like, say, for empty data β€” then the rectangle is invalid: QwtDoubleRect::isValid() == false. So check that before you go trusting it, fr fr 😭

Reimplemented from QwtData.

QwtData * QwtCPointerData::copy () const [virtual]

Returns: a pointer to a copy β€” it's a virtual copy constructor, which is lowkey the coolest kind of constructor πŸ’…

Implements QwtData.

size_t QwtCPointerData::size () const [virtual]

Returns: the size of the data set πŸ“

Implements QwtData.

double QwtCPointerData::x (size_t i) const [virtual]

Return the x value of data point i 🌈

Parameters:

  • i β€” index πŸ”’

Returns: x β€” the x value of data point i ⭐

Implements QwtData.

const double * QwtCPointerData::xData () const

Returns: array of the x-values πŸ“

double QwtCPointerData::y (size_t i) const [virtual]

Return the y value of data point i 🌈

Parameters:

  • i β€” index πŸ”’

Returns: y β€” the y value of data point i ⭐

Implements QwtData.

const double * QwtCPointerData::yData () const

Returns: array of the y-values πŸ“


πŸŽ€ Author πŸŽ€

Generated automatically by Doxygen for Qwt User's Guide from the source code. Not a human author, just a robot doing its little thing πŸ€–βœ¨


And that's the whole page, bestie β€” no crumbs left behind 🫢 This was Version 5.2.3, dated Tue Nov 20 2012, straight out of the Qwt User's Guide. Stay hydrated, keep your pointers valid, and slay πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from