Bugs in new release

[Sandra]

Hello UserLs,

Ok.It isn't a bug. You only need set to true property Clipsoft. I have added next line of code and your code works fine.

Code: Select all

    line.Marks.SoftClip = false;

Can you tell us if previous line works as you expect?

On the, other hand, TF02016127 is related to TF02015172 (and so to TF02014628). The problem in TF02015172 and TF02014628 was that MinimumOffset and MaximumOffset were not working when Axis.Automatic was set to true and now are fixed. We recognize that the behavior has changed between September of 2010 version and last version of TeeChartFor.Net, but I think the change represents the fix of a pre-existing problem. As far as I can see, the code works fine as it is now and for this reason, we consider it isn't a bug.

Thanks

[UserLS]

Thanks! I did not know about SoftClip... It works! Thanks again!

[UserLS]

On the other hand, TF02016127 is related to TF02015172 (and so to TF02014628). The problem in TF02015172 and TF02014628 was that MinimumOffset and MaximumOffset were not working when Axis.Automatic was set to true and now are fixed. We recognize that the behavior has changed between September of 2010 version and last version of TeeChartFor.Net, but I think the change represents the fix of a pre-existing problem. As far as I can see, the code works fine as it is now and for this reason, we consider it isn't a bug.

Well, I never said it was broken for automatic axes... But your fix has broken graphs with manually set Min/Max values and therefore it is a bug. In this case you've introduced another bug while fixing the original problem. Just try to explain to a normal person why, when I enter a value of 20 as an axis minimum (and this is the value displayed in your editor) the actual axis minimum is not 20, but is something less than 20. And what number should I enter as the minimum value, so the actual minimum value will be equal 20? If you have no answer to this question (one answer to all my 2000 customers about all their graphs without seeing those graphs - something I could include into help) - than this is a bug.

[Sandra]

Hello UserLs,

Images. In the version that we're using, when image is assigned to rotated mark or side walls it is rotated to make it parallel with the surface it is placed on... Not anymore. When stretched in some cases it will not cover the whole area because if this.

Can you tell us in which version this problem works fine? So we can try to fix it in last version.

Well, I never said it was broken for automatic axes... But your fix has broken graphs with manually set Min/Max values and therefore it is a bug. In this case you've introduced another bug while fixing the original problem. Just try to explain to a normal person why, when I enter a value of 20 as an axis minimum (and this is the value displayed in your editor) the actual axis minimum is not 20, but is something less than 20. And what number should I enter as the minimum value, so the actual minimum value will be equal 20? If you have no answer to this question (one answer to all my 2000 customers about all their graphs without seeing those graphs - something I could include into help) - than this is a bug.

To definition of InflateMargins said: "The InflateMargins property controls if Chart dimensions will be rescaled to accomodate the Series.Pointer HorizSize and VertSize pixels. When false, Chart Axis scales will be preserved and points close to the Axis limits will be partially displayed. " About this description I understand that the Pointer.InflateMargins should only work if Axis.Automatic is set to true (and not if set to false) and this is other reason for we arrived the conclusion of TF02016127 is not a bug. Moreover is true that fix the bugs TF02015172 (and so to TF02014628) change the behavior, but we don't consider it has broken the InflateMargin. Also, I understand you can be disagree with us and we would be very grateful if you can you explain us:
How you expect property InflateMargins works?
If you consider it must work when the axes are not automatic and for what reason?
These answers can serve us to try to arrive good conclusion for you and for us.

Thanks,

[Yeray]

Hi,

This is just to inform that the bug [TF02016154] has just been fixed. The next maintenance release will include it.

[Sandra]

Hello UserLs,

Would be very grateful if you can tell us which version are you using when this problem

"Images. In the version that we're using, when image is assigned to rotated mark or side walls it is rotated to make it parallel with the surface it is placed on... Not anymore. When stretched in some cases it will not cover the whole area because if this"

doesn't occur, so we can try to solve the problem in last version?

Thanks,