Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Releases: oxyplot/oxyplot

v2.2.0

20 Sep 12:20
989df42
This commit was created on GitHub.com and signed with GitHub’sverified signature.
GPG key ID:B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

What's Changed

New Contributors

Full Changelog:v2.1.2...v2.2.0

Contributors

  • @objorke
  • @mattico
  • @belucha
  • @rstm-sf
  • @HavenDV
  • @VisualMelon
  • @rlamp
  • @jmorgan-habs
  • @Jonarw
  • @FabianNitsche
  • @dependabot
  • @IzStriker
  • @jorgectf
  • @garydev10
objorke, mattico, and 12 other contributors
Assets2
Loading
Auto72, K486D2, hrsh, and chriglburri reacted with thumbs up emoji
4 people reacted

v2.1.2

03 Dec 11:04

Choose a tag to compare

OxyPlot 2.1.2

Small release, with the main purpose of making important bug-fixes available for the WPF provision, and removing a dependency on an insecure version of System.Drawing.Common

Added

  • Add LineThickness property to TrackerControl (#1831)
  • Add properties forMinimumSegmentLength to series and annotations (#1853)
  • Add fractal examples for PolygonAnnotation and PolylineAnnotations (#1853)
  • AddAxisPreference toPlotManipulator
  • Add VisualStudioToolsManifest.xml to add components to the Visual Studio Designer toolbox (#1446)

Changed

  • Change defaultMinimumSegmentLength to2 and remove limits for series and annotations with simple geometry (#1853)
  • Improve performance ofStairStepSeries, particularly when zoomed in and X is monotonic or when consecutive points have equal Y components
  • StairStepSeries renders a horizontal line when a point with a valid X component and invalid Y component follows a valid point
  • Update version of System.Drawing.Common

Fixed

  • WPF - OxyPlot doesn't render inside a Popup (#1796)
  • Odd behavior of zooming of Logarithmic axis in Cartesian plot (#1825)
  • SkiaSharp.WPF - OxyPlot doesn't render inside an ElementHost (#1800)
  • NullReference in SkiaSharp WPF renderer if UIElement has no PresentationSource (#1798)
  • WPF DPI Regression (#1799)
  • Code generation for escape sequences in strings (#1824)
  • Axes not always honoring AbsoluteMinimum/AbsoluteMaximum and/or MinimumRange/MaximumRange properties (#1812)
  • WindowsForms tracker no longer clipping outside PlotView boundaries (#1863)
  • Histogram now rendering properly when using logarithmic Y axis (#740)
  • Fix ExampleLibrary build errors in certain code pages (#1890)

Full changelog from 2.1.0:v2.1.0...v2.1.2

Note: there is no version 2.1.1

Loading
beibingyangliuying and Jcsurrender777 reacted with thumbs up emoji
2 people reacted

v2.1.0

04 Oct 07:42
02a21c5
This commit was created on GitHub.com and signed with GitHub’sverified signature. The key has expired.
GPG key ID:4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

OxyPlot 2.1

The primary goal of the 2.1 release is make the new SkiaSharp provisionals available:most users will be required to make code modifications if they wish to target 2.1. While this looks like a point release, there are some significant breaking changes in the API: some components have been removed, and others have been deprecated, but it should be fairly easy to port any code. Due to API changes, the 2.0 'Platform' libraries (e.g.OxyPlot.WPF andOxyPlot.WindowsForms) will not work withOxyPlot.Core 2.1, and will need to be updated:you cannot mix 2.0 and 2.1 binaries. Further details on compatability will be provided below:OxyPlot.WPF in particular has undergone significant changes.

We intend to provide 2.1 releases forOxyPlot.Avalonia,OxyPlot.Gtk,OyxPlot.Xamarin, andOxyPlot.Windows in time.

.NET Versions

  • Support for .NET Framework 4.0 has been re-introduced forOxyPlot.WindowsForms andOxyPlot.WPF. See#1452.

    Some APIs have been updated to support readonly collections. See#1600.

  • Support for .NET Core 3.0 has been removed; libraries now target .NET Core 3.1 instead. See#1488.

  • Core packages are now provided for .NET Standard 2.0in addition to .NET Standard 1.0. See#1668.

Significant breaking changes (deprecated, removed, moved, or renamed functionality that was not just a bug)

  • Legend functionality has been overhauled. The manyLegend prefix properties have been removed fromPlotModel. See#644.

    The same legend properties that previously appeared inPlotModel are supported in a newLegend class, along with additional functionality. ThePlotModel.Legends collection allows the inclusion of multiple legends on one plot.

    Hidden series are now shown in the legend by default, and visibility can be toggled by clicking on the legend entry. This new behaviour can be disabled by settingLegend.ShowInvisibleSeries = false. See#1763

  • TheOxyPlot.Wpf.Plot class and its associated components have been moved toOxyPlot.Contrib.Wpf library. A release of this library will be made soon to go with the 2.1 release. The codebase - which allows plot models to be defined in XAML as an alternative to using aPlotModel bound to aPlotView - will no longer be supported as part of the main library, but continues to function for the time being. In future, and issues with these components should be directed to theOxyPlot-Contrib repository, where we will continue to welcome community code submissions. See#1399.

    In order to make existing code work, it will be necessary to add a reference to theOxyPlot.Contrib.Wpf nuget package (once it is released), and XAML namespace references will changed to"http://oxyplot.org/wpf/contrib". This changes does not affect code using thePlotView component, which remains inOxyPlot.WPF.

  • OxyPlot.Wpf has been split intoOxyPlot.Wpf andOxyPlot.Wpf.Shared. The former depends on the latter, and is essential for all functionality.

  • Various events on plot elements have been marked as obsolete. It is better to customise thePlotController to seperate that logic from the plot elements themselves, and to avoid issues with conflicting events. See#111.

    These events will not be removed in the near future, and you can continue to use them for the time being where necessary.

  • ColumnSeries has been removed. You should replace any usage ofColumnSeries withBarSeries. See#1402.

  • CandleStickAndVolumeSeries is obsolete. Consider combining seperateCandleStickSeries andVolumeSeries. See#1661.

  • ErrorColumnSeries has been renamed toErrorBarSeries for consistency. See#1402.

  • OxyPlot.PdfExporter andOxyPlot.Pdf.PdfExporter are obsolete. Consider the newOxyPlot.SkiaSharp.PdfExporter as an alternative. See#1527.

  • Exporter APIs have been simplified and made more consistent. UsePlotModel.Background to change the background color of export graphics.

  • Reporting functionality has been moved to theOxyPlot.Reporting package. The code resides in theOxyplot-Reporting repository. See#1403.

  • VariousRenderingExtensions methods have been removed. See#1661.

  • The default color palette for color axes has been changed from 'Jet' to 'Viridis'. See#1505.

  • Axis.DesiredSize is replaced withAxis.DesiredMargin. See#1562

New features and functionality

  • OxyPlot.SkiaSharp.WPF provides an alternativePlotView for the WPF platform which uses theSkiaSharp library for immediate-mode rendering. This package targets .NET Core 3.1 and .NET Framework 4.5 and has native dependencies.

  • OxyPlot.SkiaSharp provides cross-platform JPEG, PNG, PDF, and SVG exporters based on theSkiaSharp library. The PDF exporter in particular provides a better alternative to the now obsoleteOxyPlot.Pdf provision. This package targets .NET Standard 1.3 and .NET Framework 4.5 and has native dependencies.

  • OxyPlot.ImageSharp provides JPEG and PNG exporters based on a beta realease of theImageSharp library. This is not an efficient implementation, and lacks full unicode support, but is a managed-only cross-platform option for raster graphics. This package targets .NET Standard 1.3.

  • Screen-Space axis margins. See#1623.

  • ExtrapolationLineSeries added, which allows you to declare regions of the data-space which are extrapolated data. See#1740.

Pervasive fixes

  • OxyPlot.Core.Drawing now shares its implementation withOxyPlot.WindowsForms.
  • Most X/Y Series and Annotations now support 'transposed' axes, where theXAxis is vertical and theYAxis horizontal.
  • Clipping has been consolidated across plot components, providing a more consistent user experiance.

An issue-by-issue changelog can be found thechangelog. See also thecomparison between v2.0.0 and v2.1.0.

Notes for developers

Despite the previous suggestion that only bug-fixes would be kept after the 2.1.0-Preview1 release, we've decided that the new functionality is compartmentalised enough that it's simpler to publish the develop branch as-is.

Loading
BobLd, JamesCorl, medarion, milanm, obnews, DevTechProfile, rogihee, CodingBlob, and beibingyangliuying reacted with thumbs up emojiapetukhov, fifonik, medarion, obnews, and CodingBlob reacted with hooray emojiobnews and CodingBlob reacted with heart emoji
11 people reacted

[8]ページ先頭

©2009-2026 Movatter.jp