SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and now iOS Charting & Android Chart Components
We also have a tag=SciChart on Stackoverflow.com where you can earn rep for your questions!
I have 3 questions regarding the FastHeatMapRenderableSeries
First, I would like to ask whether it possible to use the transparent color FastHeatMapRenderableSeries, even when the map itseft is opaque (Opacity=1)? I tried to include the transparent color into the ColorMap gradient brush, but then the corresponding data values are shown in white.
Second, when the heatmap is scaled, the semi-transparent cell borders are visible on the heatmap. Can I get rid of them, for example, with the UseLayoutRounding or proper scaling?
Finally, if I continuously refresh the heatmap with incoming data, I see some rendering artifacts in some frames. The artifacts are usually black vertical stripes or, more rarely, rectangles. Can it be related to graphics hardware?
I made a screenshot demonstrating all 3 problems and attached it here.
Thank you very much in advance!
The good news is, we’ve fixed a bug in SciChart’s Heatmap implementation where Alpha channel of the colour map was ignored. This has been fixed in all three renderers (High Speed, High Quality and DirectX) and has been deployed to our nightly build, v188.8.131.5235.
Regarding the cell edges, this might be intentional, I will check back with the team.
Regarding the black artefacts, we can’t reproduce this, can you send a code sample to us?
I created a simple VS2013 project that replicates the rendering artifacts on the heatmap plot (attached). I can see that the issue is related to multiple STA (UI) threads created to render the same dataseries in separate windows. When the windows are created with the main UI thread, there are no problems with rendering.
However, since I need multiple STA threads in my application, I would like to ask whether it’s possible to fix that issue? It could be beneficial for the real-time application scenarios. I tried to google for different solutions and found that the Visiblox team has experienced the similar issue:
Thank you in advance!
Please login first to submit.