modify xy graph type definition

[stevensung]

Thank you for pointing to this example. This one starts almost from scratch and every single detail has to be configured. Is there anyway that I could sort of "derive" a new xy graph control from the default one? Life will be better if that could be possible.

[altenbach]

---

@stevensung wrote:

Is there anyway that I could sort of "derive" a new xy graph control from the default one?

---

No. Just wire the data as in the upper image in the idea thread you linked. There is really nothing wrong with that.

If you still have memory or performance problems, the issue is most likely elsewhere. Can you show us some tpyical code?

[Dennis_Knutson]

Get a job at NI working in the development group. Campaign to have the Idea added to the LabVIEW roadmap. Modify the engine using your C++ skills. Test the mods and make sure the new xy graph is still compatible with the original types of inputs. Figure on releasing it in about two years at the minimum.

[JÞB]

---

@Dennis_Knutson wrote:
Get a job at NI working in the development group. Campaign to have the Idea added to the LabVIEW roadmap. Modify the engine using your C++ skills. Test the mods and make sure the new xy graph is still compatible with the original types of inputs. Figure on releasing it in about two years at the minimum.

---

That is, two calendar years.  I would suspect that more than two "man-years on project" would be required.  Given: innate knowledge of the underlying algoryhtims!   AND, bare in mind your goal is to do this with greater computational effeciency than currently available methods.  So, the minimum cost is well above 250K USD.  For what return? a Mbyte of memory for your app?  If those bytes are worth it too you I may offer my services.  (But, I usually reject contract offers that have zero chance of success.)