Thank you!

I'm one of the people regularly complaining about the need to solve the million-point problem in WPF, so I am thrilled to have another approach to try, so thank you.  I'm curious, though, if you know what relationship there might be between your approach with InteropBitmap and the new and improved WriteableBitmap class that is coming in beta in late Spring in the next update to WPF?

Thanks,

Eric

This is very intresting article.

Could you please upload the source?

Thanks

I wanted to develop a WPF project that has very intense performance requirements, and I thought it was best to consult you on this before designing the app.

The application would be rendering data obtained from a medical hardware as charts. For this, the requirements are:

1) Requires rendering of almost 250 points every 4 milliseconds in a chart (to be connected by a line or Bezier curve). The rendered points will also have a spectrum of colors (as in a heatmap).

2) The rendered points would move when new data is pumped by the hardware and rendered (as in a ECG)

3) At any given point there could be over a 150,000 moving points on the chart (because the chart window would display data of 3-5 seconds).

4) Also later we would like to retain the history of data points of past 60 seconds or so.

5) There could be upto 12 such chart displays running parallel at the same time in a window on the application.

I seek your thoughts on what could be the best approach for rendering these points and animating them. Some kind of selectively invalidating the UI would be desirable here. Also what are the recommended options for storing this much data for history purpose. The problem demands something at a very low level in the WPF stack.

How much workable would it be to draw a very specific curve using interop bitmap method. Given the requirement what will suit best?

Any Help would be highly appreciated,

Thanks in Advance