Group: Forum Members
Last Active: Yesterday @ 1:38 AM
Posts: 3,054,
Visits: 4,006
|
Hi Brad, Short update that the WPF chart control now derives from FrameworkElement and this issue is solved.
Best Regards, Nevron Support Team
|
Group: Forum Members
Last Active: Yesterday @ 1:38 AM
Posts: 3,054,
Visits: 4,006
|
Hi Brad,
We’re currently working on better WPF integration and this issue will be solved in the coming weeks.
Best Regards, Nevron Support Team
|
Group: Forum Members
Last Active: 9 Years Ago
Posts: 5,
Visits: 40
|
There are several people that have figured it out, including this guy: http://jmorrill.hjtcentral.com/Home/tabid/428/EntryId/61/Over-coming-the-Interop-Airspace-Issue-in-WPF.aspxThis is a very critical issue that is causing a few really bad rendering issues, some of which will require significant amounts of work to work around. Is there an ETA on a proper WPF version?
|
Group: Forum Members
Last Active: Yesterday @ 1:38 AM
Posts: 3,054,
Visits: 4,006
|
Hi Brad,
Not yet however we plan to implement the WPF control in a different way (currently it uses WinForm control host) so that it does not have this problem.
Best Regards, Nevron Support Team
|
Group: Forum Members
Last Active: 9 Years Ago
Posts: 5,
Visits: 40
|
I have a WPF app with the Nevron chart rendering an NCartesianChart. When ever there is a WPF element on top of the chart (such as a loading slash), the chart still renders on top. Is there a fix/workaround here?
|