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, If x-axis is on top and y-axis is reversed, then the border for the BackgroundElements for the bottom part disappeared. If y-axis is on right and x-axis is reversed, then the boder for the BackgroundElements for the left part disappeared. This is not in Version 5.0 Sept. 26, 2013 nightly build. You can modify the line samples to see the effective. The included is the screenshot for Version 5.0 and Version 6.0 for comparison. I used Jan13 Version 6.0 nightly build. Thanks, Gordon |
|
|
|
|
Hello Gordon Unfortunately I have not been able to reproduce this by modifying our line samples. Just to clarify, are you achieving this result by adding a Border object into the BackgroundElements collection? I have had trouble with this in the past - even in 5.0. Since the border ends up right at the edge of a clipping region, WPF sometimes fades the color of the border to get an anti-aliasing effect, or sometimes even hides a 1 pixel edge of the border. I've tried all sorts of things such as snapping to device pixels, disabling anti aliasing and forcing the width and height of various parts of the chart to be integers. It seems that the results can also vary based on the sizes of components around the chart. For example if there is a window with a Chart and a Menu, the auto height of the menu will be a floating point value which can cause this clipping issue. But if I force the height of the Menu to be an integer, then the issue is resolved. Another thing I've tried is to extend the clipping region by 1 pixel, but this sometimes causes an extra pixel of the grid lines to appear outside the border which is also undesired. It seems when a clipping region is involved, the usual tricks for solving this kind of problem don't work. I do have an idea to resolve this in version 7.0, but for now, maybe you could add a margin to the border to push it 1 pixel into the chart. -Jason Fauchelle |
|
|
|
|
Hi Jason, I am achieving this result by adding a Border object into the BackgroundElements collection. As you mentioned, It also eats the GridLine if we did not put the Border. if we put the border's margin = new Thickness(0,0,0,1), it will solved the problem, but as you mentioned, it will have border one pixel above the correct position. When version 7 comes out? How big changes between version 6 and 7? Can you put the ideas in version 6? Thanks Gordon |
|
|
|
|
My idea involves moving up to a higher version of .NET which has improvements around these kinds of pixel issues. This can only be done in a major version. But as I haven't tried it yet, I can not guarantee that it will work for this scenario. We are planning to wrap up version 7 soon. It does not have any API changes. |
|
|
|
|
Is .Net4.0? Windows XP can only have .Net4.0 though. Since a lot of our clients still uses Windows XP, so we cannot move up our products higher than .Net4.0 yet (even though Microsoft will not support XP soon.) |
|
|
|
|
Yes .Net 4.0 is the plan. But I will also look at alternative solutions for you too. Though from my past experience in this issue, an alternative solution is not looking very promising. I'm haven't been able to get a stable repro case either, but I'll let you know how it goes. -Jason Fauchelle |
|
|
|
