You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 17, 2023. It is now read-only.
@beto-rodriguez You said that "UWP needs 2 paths to display correctly the fill of any LineSeries". Are you implying that there is a workaround for this issue? Can you elaborate please?
I already fixed it in my local 'designcleanup' branch, in general in this branch I am cleaning the design issues I faced to extend the library to UWP, this fix should be soon uploaded in this repo.
In WPF I was able to create a Path object, at the beginning and end of the Path I added a LineSegment, in WPF the LineSegment object has the IsStroked property, it is set to false, sadly in UWP we don't have this property, so the best workaround I could think of, is to add 2 different paths, the First one will draw only the stroked line, and the second one will draw the fill of the LineSeries
@beto-rodriguez I too have experienced the pains of missing items from UWP. I am anxiously awaiting that fix 馃槃. Your library is awesome, and I appreciate all the work that you continue to put into it! 馃挘
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Due incompatibility with WPF structure, UWP needs 2 paths to display correctly the fill of any LineSeries otherwise we get this ugly lines...
Version 0.8 introduces UWP 馃帀 and will not include this fix for now
The text was updated successfully, but these errors were encountered: