jQWidgets Forums
Forum Replies Created
-
Author
-
February 8, 2019 at 8:11 am in reply to: Grid Server Paging totalrecords has no effect Grid Server Paging totalrecords has no effect #103900
Hi Hristo,
thanks for your advice. The server result was fine and there was no error. So I started going over the tutorial again line by line and I found my error.
It’s this:beforeprocessing: function (data) { dataSource.totalRecords = data.TotalRows; }
I used camel case for totalrecords instead of all small letters. Once I fixed that, it worked fine.
February 5, 2019 at 9:40 am in reply to: Grid Server Paging totalrecords has no effect Grid Server Paging totalrecords has no effect #103861Hi Hristo,
thanks, but that’s what I tried first, following the tutorial. When that didn’t work I looked around for other examples; I got passing the adapter records in the rendergridrows method there.
Both options don’t work.Is there some additional option I have to set for GridView to recognize totalrecords?
Hi Peter,
I’m aware that the text input change event is raised on blur and that this is the correct behaviour.
I just think that the text input should be blurred (and thus raise the change event) before the check change event is raised. The way it works now seems to be: click on checkbox > check change event > checkbox gets focus > text input blur > text input change event. In my opinion it should be: click on checkbox > checkbox gets focus > text input blur > text change event > checkbox change event.Please consider that if I use a button, the order of events is exactly as I expect: when clicking a button, the text input loses focus (raising its change event) before the button’s click event is raised. I don’t see why it has to work differently for a checkbox.
Regards,
AnneHi Hristo,
please see this JSFiddle for a simplified example. Write something in the textbox, then immediately check the checkbox without clicking anywhere else first. You will see that the checkbox change event is called before the text input change event.
This is contrary to the expected sequence of events. As I said in my original comment, this can be problematic, if you want to do additinal data processing in the check change event.
The workaround I described works of course, but if you encounter this problem for the first time, it takes a while to even find the cause.Anne
-
AuthorPosts