Maximum range meaning between the visible min and max points? 'cause that sounds like a pretty decent way of limiting it (also as wbidus mentioned MinimumRange already exists =P). I've said this a few times already but it'd also be nice if the AxisChanged event had more information in it's event args (like factor or new screen points).
↧
New Post: Maximum zoom-in limit
↧
Commented Feature: Improve tracker style (Windows Forms) [10125]
Currently it is implemented as a simple label. Should be improved:
- move it away so the mouse cursor does not obscure it
- add padding
- add border
- make colors (text, border, background) customizable
- make it possible to hide it completely?
Comments: Any feedback?
- move it away so the mouse cursor does not obscure it
- add padding
- add border
- make colors (text, border, background) customizable
- make it possible to hide it completely?
Comments: Any feedback?
↧
↧
Commented Unassigned: LineSeries: OutOfMemoryException when Smooth=true [10227]
Refer to discussion:
https://oxyplot.codeplex.com/discussions/550416
Exception at : CanonicalSplineHelper.Segment(). Line207.
How to reproduce this:
1. Set lineSeries.Smooth = true when create lineSeries.
eg: var ls = new LineSeries { Title = title,Smooth = true};
2. Zoom in by pushing down mid-mouse button, create rectangle zoom area.
3. After several times, out of memory exception throws.
Comments: Oh, Yes. it is duplicated. Could you remove this one. Thanks.
https://oxyplot.codeplex.com/discussions/550416
Exception at : CanonicalSplineHelper.Segment(). Line207.
How to reproduce this:
1. Set lineSeries.Smooth = true when create lineSeries.
eg: var ls = new LineSeries { Title = title,Smooth = true};
2. Zoom in by pushing down mid-mouse button, create rectangle zoom area.
3. After several times, out of memory exception throws.
Comments: Oh, Yes. it is duplicated. Could you remove this one. Thanks.
↧
Source code checked in, #410139defa7d
Wpf: TextFormattingMode should be consistent for text measuring and drawing
Setting default text formatting mode to Display.
↧
Source code checked in, #290668bad113
Wpf: revert change from revision 1135
↧
↧
Source code checked in, #488165d54ac4
#10221: Wpf - move conversion methods to render context class
↧
Commented Issue: OxyPlot.Wpf - Bad rendering on different display scaling levels [10221]
The plot is not rendered as expected if the display scaling level is not set to 100% (see attached picture)
Comments: I committed some TODOs in the ShapesRenderContext class where I think this should be corrected. I have also moved the pixel snapping methods into this class.
Comments: I committed some TODOs in the ShapesRenderContext class where I think this should be corrected. I have also moved the pixel snapping methods into this class.
↧
Source code checked in, #1b1250a8fcdc
#10230: move the ToolTip property to the PlotElement class
↧
Closed Unassigned: Add ToolTip property to PlotElement [10230]
Add ToolTip property
Remove ToolTip from Axis class
Add a virtual Render method to PlotElement that sets the tool tip.
Remove ToolTip from Axis class
Add a virtual Render method to PlotElement that sets the tool tip.
↧
↧
New Post: Moving the project to GitHub
IMHO just go create a mock up github repository and github.io page, and play around with it, then decide if you like it over codeplex. No harm in giving it a try right?
↧
New Post: Maximum zoom-in limit
Yes, it should be the minimum between minimum and maximum. Sorry, I forgot that it was already implemented. And default value should of course be 0...
@Slxe: I think we can start a new discussion/issue on changing the AxisChanged event data. I am a bit hesitant to exposing more data than what is absolutely needed :-)
@Slxe: I think we can start a new discussion/issue on changing the AxisChanged event data. I am a bit hesitant to exposing more data than what is absolutely needed :-)
↧
Commented Feature: Improve tracker style (Windows Forms) [10125]
Currently it is implemented as a simple label. Should be improved:
- move it away so the mouse cursor does not obscure it
- add padding
- add border
- make colors (text, border, background) customizable
- make it possible to hide it completely?
Comments: Great work! I need some time to ´digest` and test this. And I will be mostly offline the next 3 weeks. Can anybody else using WinForms give their input?
- move it away so the mouse cursor does not obscure it
- add padding
- add border
- make colors (text, border, background) customizable
- make it possible to hide it completely?
Comments: Great work! I need some time to ´digest` and test this. And I will be mostly offline the next 3 weeks. Can anybody else using WinForms give their input?
↧
New Post: Moving the project to GitHub
Yes, I will do some testing later!
The main reason for changing would be to make it easier to collaborate and manage contributions. It would be interesting to know if changing to GitHub would make more people interested in contributing to the project!
But the lack of discussion forum + loosing issue and discussion history + the work of moving 157 issues could be reason enough to stay with CodePlex...
The main reason for changing would be to make it easier to collaborate and manage contributions. It would be interesting to know if changing to GitHub would make more people interested in contributing to the project!
But the lack of discussion forum + loosing issue and discussion history + the work of moving 157 issues could be reason enough to stay with CodePlex...
↧
↧
New Post: LegendSymbolZoom property is possibly required when rendering ScatterSeries with a tiny MarkerSize
const double markerSize = 0.5;
var plotSource = new ScatterSeries
{
MarkerFill = OxyColor.FromAColor(235, OxyColors.Black),
MarkerSize = markerSize,
MarkerStroke = OxyColors.Transparent,
MarkerStrokeThickness = 0,
MarkerType = MarkerType.Square,
Title = "人工作业"
};
PlotModel1.Series.Add(plotSource);I suggest introducing a LegendSymbolZoom property to PlotModel class so that we're able to specify the displaying size for symbols of the legend.
↧
New Post: Why not make RenderContext of Plot selectable by user
objo wrote:
Supporting directly downloading with IE:
Download OxyPlot.Wpf.Extension (for WPF only)
And, objo, may you feel like this one: Change Current DrawingContext to one using OpenGL
It would be very interesting to see how you have implemented this render context based on writable bitmaps!Hi objo, I don't know how to create a fork and make a pull request. I put source code on a network disk. You can download it yourself.
Can you create a fork? Then make a pull request, and I will review!
Supporting directly downloading with IE:
Download OxyPlot.Wpf.Extension (for WPF only)
And, objo, may you feel like this one: Change Current DrawingContext to one using OpenGL
↧
New Post: Change Current DrawingContext to one using OpenGL
Last year I tried to make a BitmapDrawingContext using WriteableBitmap. It brought lots of Performance improvement to my project. Err, I put a lot of effort to let WriteableBitmap draw text with transforms on WPF. Maybe there's many improvements needed to be done in BitmapDrawingContext, It works quite for me yet. One thing I should point out that the performance bottleneck of BitmapDrawingContext is DrawText, and there's no solution for it.
Recently, I had a try on OpenGL and soon fell in love with it:)
Why I finally choose OpenGL? Here're some reasons.
*Best performance!Hardware acceleration!
*cross platform: Windows, Unix, Linux, Mac OS，Andorid，WP....
*supporting .net on all platform with the help with Mono project, but only window support WPF.
*More Low-Level APIs which are easy to use.
To use OpenGL cross platform, I recommend OpenTK(Open Toolkit). The Open Toolkit is an advanced, low-level C# library that wraps OpenGL, OpenCL and OpenAL. There's another outstanding OpenGL library on .net framework whose name is SharpGL. However SharpGL just supports Windows while OpenTK supports all.
To make a new DrawingContext is not easy, I think it's necessary to give some changes to PlotView in order to maintain compatibility with existing DrawingContexts. So do you agree with me, objo?
In the end, BitmapDrawingContext is available for you all:
Supporting directly downloading with IE:
Download OxyPlot.Wpf.Extension (for WPF only)
Recently, I had a try on OpenGL and soon fell in love with it:)
Why I finally choose OpenGL? Here're some reasons.
*Best performance!Hardware acceleration!
*cross platform: Windows, Unix, Linux, Mac OS，Andorid，WP....
*supporting .net on all platform with the help with Mono project, but only window support WPF.
*More Low-Level APIs which are easy to use.
To use OpenGL cross platform, I recommend OpenTK(Open Toolkit). The Open Toolkit is an advanced, low-level C# library that wraps OpenGL, OpenCL and OpenAL. There's another outstanding OpenGL library on .net framework whose name is SharpGL. However SharpGL just supports Windows while OpenTK supports all.
To make a new DrawingContext is not easy, I think it's necessary to give some changes to PlotView in order to maintain compatibility with existing DrawingContexts. So do you agree with me, objo?
In the end, BitmapDrawingContext is available for you all:
Supporting directly downloading with IE:
Download OxyPlot.Wpf.Extension (for WPF only)
↧
New Post: Android - W/OpenGLRenderer(): Path too large to be rendered into a texture
I'm not sure what I'm seeing here, thought I would ask and see if anyone else is seeing this.
Xamarin.Android column series, I setup a value axis with the following parameters:
I'm a bit stumped on what is going on here or what I might do to correct it, thoughts?
-ben
Xamarin.Android column series, I setup a value axis with the following parameters:
var valueAxis = new LinearAxis { Position = AxisPosition.Left, MinimumPadding = 0, MaximumPadding = 0.06, Minimum = 260, Maximum = 265 };07-13 14:24:50.911 W/OpenGLRenderer( 3926): Path too large to be rendered into a textureMinimum to 100, graph draws fine, but when I do a two finger zoom in the graph fails to draw and the output window starts outputting "Path too large..." errors.I'm a bit stumped on what is going on here or what I might do to correct it, thoughts?
-ben
↧
↧
New Post: System.InvalidOperationException - OnKeyDown
In my case this error occurs only after moving the chart. when i press 'a' key just after plot loads, nothing happens. When I move the plot and press 'a', exception appears.
An unhandled exception of type 'System.InvalidOperationException' occurred in mscorlib.dll
Additional information: Collection was modified; enumeration operation may not execute.
An unhandled exception of type 'System.InvalidOperationException' occurred in mscorlib.dll
Additional information: Collection was modified; enumeration operation may not execute.
↧
New Post: System.InvalidOperationException - OnKeyDown
Yea I've gotten that error a few times myself, but it generally cleans itself up. That's happening because you're moving or altering OxyPlots display, which is somewhat based on the data in each series points list, at the same time that data is being added to those points lists. I found it all depends on how often you're refreshing the displayed chart (calling InvalidatePlot(true)), in playing with it myself, in WinForms though, I've found generally anything under about 200ms starts getting pretty buggy because of these conflicts. Also keep in mind that that includes when you add data to the points lists, as zooming and panning calls InvalidatePlot(false).
↧
New Post: Adding more information to AxisChangedEventArgs
I'd like to propose adding some more information to AxisChangedEventArgs, just simple things like the original screen points used for a zoom or pan, and the scale or factor used.
The main reasoning behind this for me is that this will make things like syncing axis changes easier. For example if you have two or three axes displayed on the left side, being able to use the same screen coordinates for panning would be a lot easier than having to Transform then InverseTransform the ActualMin/Max values to try and sync them.
I'd also like to suggest adding more types to AxisChangedTypes, for the different kinds of zoom (scale, range and factor) and pan (screen points and delta), again for similar reasons as above.
The main reasoning behind this for me is that this will make things like syncing axis changes easier. For example if you have two or three axes displayed on the left side, being able to use the same screen coordinates for panning would be a lot easier than having to Transform then InverseTransform the ActualMin/Max values to try and sync them.
I'd also like to suggest adding more types to AxisChangedTypes, for the different kinds of zoom (scale, range and factor) and pan (screen points and delta), again for similar reasons as above.
↧