This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi there, When we zooming a bar graph which uses logarithmic for one axis (another axis is string value), then the following message comes up: "New guard page for the Stack cannot be created". Please see the video loaded Thanks, Gordon |
|
|
|
|
Hello Gordon This message is not coming from WPF Elements. I haven't been able to reproduce any kind of crash when zooming far into a chart with a logarithmic axis. Let me know if you find a way to reproduce this if it is related to WPF Elements. -Jason Fauchelle |
|
|
|
|
Hi Jason, Even though the message is not from WPFControl, but I think it is still in your code when zooming. Here are the call stacks when it is happened (just gives you a few): Mindscape.WpfElements.dll!Mindscape.WpfElements.Charting.ChartAxis.ActualMinimumValue.set(double value) + 0x599 bytes I see in your code on ChartAxis.ActualMinimumValue has the following line: else if (ActualMaximumValue - ActualMinimumValue < MinimumRange && MaximumValue - MinimumValue > MinimumRange) When you do operation on double value, it is very tricky, for example, ActualMaximumValue - ActualMinimumValue should be 2.96, but it will gives you 2.960000000000001 or 2.9599999999999996... |
|
|
|
|
Hello Gordon Thanks for the additional information. This looks like the same stack overflow issue that I thought I'd resolved not long ago. I have not been able to reproduce any issues caused by the precision of the minus operation. Without being able to reproduce this, it may be a bit risky trying to put in a solution. There are 2 options that we can try: You could send me a simple repro project, or let me know how to reproduce this issue with one of your recent repro projects. Or, by using the source code that you have, you could try find a solution to this problem. If the solution is simple, let me know and I'll try it out and check that all the unit tests and manual tests are fine. Let me know what you'd like to do. Is this issue occurring consistently, or does it sometimes work fine. Also, which version of WPF Elements are you using? -Jason Fauchelle |
|
|
|
