Completed
Last Updated: 22 May 2019 12:02 by ADMIN
TW
Created on: 16 Dec 2018 00:00
Category: GridView
Type: Bug Report
2
RadGridView DeferredSearching_WPF.sln search as you type not working for 'long' instead of 'int'

Users reported that the Text Search feature is misbehaving for certain columns in their grid.

We found that that if we take the Telerik example “DeferredSearching_WPF.sln", and change the "int" field+property to "long" , text search for a number indeed falls over.

Can you reproduce this?

Kind regards, Bertus Distributie ICT

8 comments
ADMIN
Martin Ivanov
Posted on: 28 Dec 2018 13:36
Hi Tijs,

Correct. This is exactly what I meant. 

Regards,
Martin Ivanov
Progress Telerik
Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
TW
Posted on: 28 Dec 2018 12:51

Hi Martin,

 

Understood. By "follow the feedback item",  you mean "Follow notifications on this issue" ? If so, sure, I'm not unsubscribing this issue of course.

 

Kind regards, Bertus Distributie ICT

ADMIN
Martin Ivanov
Posted on: 28 Dec 2018 12:45
Hello Tijs,

I am glad to hear that you have a workaround for this. As for the fix' timeframe, I am afraid that at this point we can't give any promises, but, I could advise you to follow the feedback item. This way you will get notified as soon as its status changes to "In Development".

Regards,
Martin Ivanov
Progress Telerik
Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
TW
Posted on: 24 Dec 2018 15:54

Hi Stefan,

 

Thank you for confirming this.

We'll have to wait for a future version of Telerik WPF to support this, as it seems.

 

Please let me know as soon as there's a known timeframe to fix this.

In the meantime, I guess we'll have to go for dummy 'double' properties in our DTO, that cast back and fro to long. Ugly, but alas. We didn't find any simpler workaround.

Kind regards, Bertus Distributie ICT

ADMIN
Stefan
Posted on: 24 Dec 2018 15:45
Hi Tijs Wickardt,

Thank you very much for your patience.

Indeed, the current version of RadGridView does not support searching for a long data type. Thus, I have set the status of this item to approved. I am afraid that I cannot propose a workaround for this case. I have also updated your Telerik points as a small token of gratitude for your cooperation.

Let me know in case I can be of further assistance.

Regards,
Stefan
Progress Telerik
Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
TW
Posted on: 21 Dec 2018 17:27

Hi Stefan, thank you for the update.

Monday would be great.

 

ADMIN
Stefan
Posted on: 21 Dec 2018 16:56
Hello,

Thank you for the detailed report.

I am investigating the case, but I need a little more time for this. I will do my best to update you on Monday.

Thank you in advance for understanding.

Regards,
Stefan
Progress Telerik
Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
TW
Posted on: 17 Dec 2018 08:27

Just some extra clarification:

In Player.cs, we changed:

public int Number 

to

public long Number

and we changed:

private int number;

to

private long number;

 

and the result is this:

Type '25' ->

While it should be (using 'int' instead of 'long'; original):

 

We also tested with 'double', and that works. Only 'long' seems to have a problem.

We are also interested in workarounds. Just adding a 'double' to our model is one workaround ('int' not possible, the numbers are too long), but that's very crude (the model comes from a separate generated assembly, modelled after an rdbms).
We tried an IValueConverter that converts long to double, but that didn't solve the problem. We also tried an ObjectDataProvider , but that didn't solve the problem. We tried our string indexer (which all rows in our data have) but that didn't solve the problem.

We're hoping you can help us out within a few days. 

Kind regards, Bertus Distributie ICT