showfilterrow 'filter' event

[arajputMember]

Hi,
I am using the showfilterrow: true property to enable the row filtering and then listening on the ‘filter’ event, also I am doing server-side filtering/pagination.

Issue I am running into is that the filter event gets triggered every time i type in a character in the filter row input field. I would like to change this behavior to do the actual filtering on the ‘Enter’ key event.

Even though the actual ‘event’ argument object (in the filter event callback function) is a JQuery.Event object, I am not seeing the actual event info like the ‘charCode’ or the ‘keyCode’, also calls to event.which returns an undefined

Any help/suggestions would be greatly appreciated.

Thanks!
Ashish

[Peter StoevKeymaster]

Hi Ashish,

It is not possible to change the built-in behavior for filtering. The Grid does filtering when the user types something in the text filters. In case you do not want that behavior, you can turn off the filter row and use filtering through the Context Menu as in the Filtering demo.

Best Regards,
Peter Stoev

jQWidgets Team
http://www.jqwidgets.com/

[arajputMember]

Hi Peter,
Currently the ‘filter’ event get triggered by ‘all’ key events. I am mainly looking to differentiate between a key type event and an ‘Enter’ event, and not change the built-in behavior.
Is there a plan to encapsulate that information (key code/char) in the next release or so? also confirming first if its not already there?
This would really help as not everyone would want the grid to start filtering as soon as any key event is detected, also if its a server-side filtering (in my case), it would put a lot of additional unnecessary load on the server. if thousands of users are searching.

Thanks
Ashish

[Peter StoevKeymaster]

Hi Ashish,

That is the built-in behavior. The Grid is filtered when a key is pressed on a focused filter textbox. We will consider adding additional API options for customization in the future.

Best Regards,
Peter Stoev

jQWidgets Team
http://www.jqwidgets.com/

[arajputMember]

Peter,
So basically none of the original keystroke info is captured in this ‘event’ object? Can you please confirm this?

[Peter StoevKeymaster]

Ho arajput.

The Filter’s Event is not related to the Key Events so you cannot use arguments from a Key event. Filter event is raised when the filter is changed which can be done in various ways – through API, through mouse clicks or keyboard.

Best Regards,
Peter Stoev

jQWidgets Team
http://www.jqwidgets.com/

[arajputMember]

I am doing it through keyboard

[arajputMember]

The Filter event is for sure triggered because of a key event, so how are they not related. Key event is the original source, so shouldn’t it be captured. I feel like I am repeating my point multiple times and not getting an answer.

We are about to purchase an enterprise license, is there a way I could get a support ticket open on this and have your team look into it?

I hope you understand the problem, the ability to add logic based on the original key event is quite important to us.

Thanks
Ashish

[Peter StoevKeymaster]

Hi Ashish,

As I already posted, “filter” event is raised when the Grid’s Filter is changed. That event does not hold information about other events like KeyDown, MouseDown, etc and it should not hold such information. “filter” can be changed by typing into a textbox, setting a value through the mouse, or through the Grid’s API. That does not mean that the “filter” event should hold mouse information, key information, etc. The “filter” event works as it is designed and we do not see a reason to change its logic. In a future version, we will consider extending the TextBox Filter’s API.

Best Regards,
Peter Stoev

jQWidgets Team
http://www.jqwidgets.com/

[Author]

Posts