If Axis RangeMax<RangeMin - chart data displays fine but NO axis/labelsusing latest NetAdvantage_WinForms_20091.2050Same bug if you set RangeMin<RangeMax anduse the Margin Near/Far = 100 featureThis used to work fine and is critical to our program :¬(Any idea what to do ?I will look at the source code and report a fix if i see it.Thanks
yes, i can recall that working at some point, at least with the margins, but it was never considered supported behavior (i.e. it was not part of our regression tests) and i don't think it has worked like that for many versions.
i have entered a bug report, so we will get this fixed for you. the bug number is 21979. feel free to contact Infragistics Developer Support at any time to inquire about the status of the bug.
if you need a temporary workaround, handling the FillSceneGraph event and adding the Text primitives in there could be done somewhat easily.
as for the Ink build errors, I'm not sure why you'd get these from the chart source code, since the chart has no such dependencies.
Hi David,Thank you for adding the bug reportThe Ink problem was happening because i was trying to build the whole source
I didn't realize the charting had its own separate solution :¬)
try visiting this page: https://ko.infragistics.com/Membership/Default.aspx?panel=Downloads#HelpCenter
it should give you a list of bug reports linked to your account.
21979 was fixed on 12/14/2009 and should be resolved in the latest service release for 9.1 and 9.2.
FIrstly we have for over 4 years had a good tech relationship<just trying to establish we have agreed before etc>
but as you said...Try visiting this page: https://ko.infragistics.com/Membership /Default.aspx?panel=Downloads#HelpCenterDoes not help as its a generic entery point into your help system
I have not been able to ever use your help/bug sytem as anything after 2007 never turns up (please refer to my original email with URL link to prove this)
you told me ...21979 was fixed on 12/14/2009 and should be resolved in the latest service release for 9.1 and 9.2.But Sadly we find this to be stil broken with 2009.2 .2049 hot fix
Many thanks for your help
bmcloughlin said:FIrstly we have for over 4 years had a good tech relationship
that's why i answer your posts first whenever i see them :)
sorry that resulted in misinformation! i should have exercised a bit more care, but i must have been overexcited about some code i was going to write.
for the link i sent you: if you visit that page, there should be a listbox on the left- click "help center" and the page should display bugs and support cases linked to your account. unfortunately, i don't think this system can be used to look up a bug if you have never contacted Developer Support about it in the past. I emailed DSManager about that to confirm, and will post back here if it turns out there is a way.
the system on DevCenter is no longer in use, so, sorry for the years of confusion that might have caused you. we are migrating to a bug tracking system based on TFS, with some customer-facing pages like "my bugs," but at this time there is no equivalent page to the one you linked to.
as for 21979 - as it turns out, this is fixed in 9.2.20092.2050. the next service release will certainly have the bug resolved. if you need the fix earlier, i think Developer Support can provide you with an untested build if you contact them about it.
have a nice weekend!
Hi David,
Many thanks for the update on this bug.
I noticed a new service pack available 2058 todayI will go and check if the problem is fixed and i will report back later
Saddly even after following your detailed instruction on how to use the helpcenter,It totaly fails to report anything for me, reports or bug fixes
I guess somethings gone wrong with this part of my account
I now realise this is not the place to vent frustrations over this devcenter/helpcenter thing and I will contact the people directly.
Thank you for your help.
Hi again :¬)After testing 2058 it appears the fix was implemented this way.....
Correct handling of RangeMin>RangeMax :¬) (inverts the axes and data) but...this means you cant use RangeType:Automatic only RangeType::Custom
The old way to mess with the margin extent percentages does not workI can recode to calculate my own range min and range maxes so this is a good fix for me
Many thanks