This is a migrated thread and some comments may be shown as answers.

Dragging column headers has ghost far away

16 Answers 102 Views

GridView

This is a migrated thread and some comments may be shown as answers.

16 Answers, 1 is accepted

answered on 27 Oct 2011, 10:00 AM

Hello Didie,

I can confirm that the issue is solved using the latest internal build...

However - and this is a very, very BIG however - telerik introduced so many breaking changes (we are using for this particular application version 2010.2.924.40 of the radcontrols) that I can't justify to anyone at my company to spend thousands on fixing your breaking changes and then spend thousands more on regression testing - a quick look at your breaking changes seem to suggest that your devs are doing it only for the sake of it (moving properties around to templates etc) due to (presumably) some weird best practices - we as a company are ONLY interested in consistency and continuity and that you as a supplier only fix bugs, not move code around because you can!!! This is very frustrating and seems like a waste of time and money..... please relay this to whoever is responsible!

Regards

Patrick

answered on 27 Oct 2011, 10:44 AM

Hello Vlad,

I will not list all the changes I had to make just to make the code compile, but I can assure you there were a lot, just a couple of examples:

the RadBusyIndicator errors now with:
"Set property 'Telerik.Windows.Controls.LocalizationManager.ResourceKey' threw an exception."

- or the Member property of the e.GroupDescriptor is gone

- IsTodayHighlighted on the RadDatePicker is gone

- the RadDatePicker doesn't use its specified custom template anymore (and looks like an ordinary one) - not even an error message is given...

I can go on like this with Int32 properties that changed to structs and dependency objects that are suddenly windows setters or conflicting namespaces.

And this is just to compile the application...

When we then run the application it errors on every screen with for example:

- out of range exceptions for our procedures that use the System.Windows.Media.VisualTreeHelper

- or value converters have errors because return values of dependency objects have changed....

and a couple of more for which I can't follow the stack trace at the moment because of the IoC / prism stuff....

I appreciate that between our version of the controls and the latest internal build a lot of time has past, but realistically we have to roll out the applications at some point and can't keep up with what you guys are doing - please consider this as I am certain that others will have the same trouble!

Regards

Patrick

answered on 31 Oct 2011, 10:44 AM

Hello Patrick,

I am sorry to hear about your frustration while using our RadControls for WPF.

We are constantly working on improving our controls. Unfortunately the bugfixes and the new features often require changes in the public API and the XAML. We try to keep these changes to the possible minimum but in these rare cases we provide obsolete properties and methods, and we keep them for at least one release cycle (four months minimum). Unfortunately if you use obsolete properties, there will be no warnings and you will get errors when we delete the properties. This is why we are doing our best to provide detailed release history where all changes are listed, blog posts which give more explanations how the new features should be used, Latest Internal Build each Monday to provide an early preview of what is coming with the next SP or official release. You can check all changes since Q2 2010 SP2 here.

Kind regards,
Hristo
the Telerik team

Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>