Conversation
This was referenced Nov 25, 2023
Member
Author
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


OpenGL rendering can cause issues when displaying multiple controls (#3007) and problems for rendering on newer hardware platforms (#2950)
This PR creates separate
FormsPlot,FormsPlotGL,WpfPlot, andWpfPlotGLcontrolsOne advantage is that the
WpfPlotcan use the officialSKElementand not the unofficialSKGLElementwe've been carrying in ScottPlot's code base (#2395) because it doesn't seem to be in the official package yet mono/SkiaSharp#2317I don't think this is an ideal long term solution. A better solution would be an easier way for users to opt-in to OpenGL acceleration using the same control. This was feasible for the WinForms control, but I had trouble getting this to work in the WPF control because of issues related to templating (#2565)