[chuckmParticipant]

Hello!

Sorry to reply so late but my company was working on many things which kept me very busy!

The example above actually proves my point that things are in the wrong order and doesn’t really address the issue discussed. The events still happen in the wrong order, you’ve simply delayed the notification of the so-called “click” event to the user but the cell is already selected in the grid prior to the blur and so-called “click” event notification. Again, this IS the issue I’m referring to.

If the “blur” were actually happening prior to the “click” event, then the cell would not be highlighted before the “blur” and “click” events occur, but it is. This means that the actions ON THE GRID are happening PRIOR TO the “click” notification being sent to the developer. This is the opposite of what a true “click” event does.

A true “click” event notifies you that a click has occurred on an object PRIOR TO anything happening to the object clicked. This allows the developer to do anything they want, including preventing the click from performing any action (say, for example in this case, based on data validation of the data in the current row).

Since a “mouse-down” like event is being used in the grid, the actions on the grid are taking place FIRST (and shouldn’t). Therefore, there is no way to perform an activity on the current row prior to another row or another object from being selected. There is no way to short-circuit or prevent the results of the click event due to other page events.

To see this more clearly, simply change the setTimeout(handler) to setTimeout(handler, 3000), you’ll see that the user action takes place immediately (clicking a cell which is then IMMEDIATELY HIGHLIGHTED in the grid) but the user doesn’t get a notification of that event until 3 seconds later. You SHOULD get a “blur”, then a “click” event, and THEN the cell should be highlighted.

Thank you!

[chuckmParticipant]

Well, I did ask a question above. Could you please answer the question? I’m not sure how many people understand this is an issue but it does cause problems for people using the grid and page events:

“I realize that it may not be possible for you to completely restructure your events in your grid, but would it be possible to add a rowClick event at the right place (after the mouseup)? The current rowClick is actually a mousedown.”

Either updating the events properly or at least giving an option to configure them would be incredibly helpful.
Thank you!

[chuckmParticipant]

Ah, a timing thing, good deal, done and thank you!

[chuckmParticipant]

Here is a demo to show the issue: https://codesandbox.io/s/check-all-checkbox-sometimes-disabled-lg207w?file=/src/app/app.component.ts

Thank you,
Chuck

[chuckmParticipant]

Thank you!

[chuckmParticipant]

Yes, that’s correct. For instance on the onRowSelect event. This event fires when the row is selected by a user and programmatically. Is there a way to determine if it was based on a user event vs a call within the code?

Thank you,
Chuck

[chuckmParticipant]

Good morning,

I may be reading you answer incorrectly but….as noted above, I understand that there is an “args.type” for the dropdownlist and I am using it. I’m asking if there is a similar property for the jqxGrid? Does the jqxGrid have a property that I can reference (similar to the dropdown) that indicates whether a keyboard, mouse or programmatic call was made?

Thanks again,
Chuck

[chuckmParticipant]

Oh, one small thing…it does appear to fire the “onblur” event after you tab off the jqxpasswordinput under the onChange event.

I’d expect the onchange to fire when anything in the edit is typed but the onblur to fire when tabbing off the field.

[chuckmParticipant]

By the way, I’m using jqWidgets-ng version 14.1.17.

[chuckmParticipant]

Thank you!

[chuckmParticipant]

Hello again Svetoslav!

I’ve tried the .updaterow() function along with a beginupdate/endupdate pairing and this seems to work. I’ll go this route and hope it all works out!

I do hope you will look at this item and consider it a bug and update to have it working the same with or without a filter.

Thanks very much for your help.
Chuck

[chuckmParticipant]

Sorry, also, just wondering if this is still considered a bug since it works differently with and without a filter applied? I would assume so.

Thanks again,
Chuck

[chuckmParticipant]

Hello Svetoslav!

This certainly works for the example I’ve given, and perhaps I should’ve made it more complicated to clearly display the issue further, but what if multiple values on a row are updated on the data related to a row in the grid? Say, a selection in the dropdown causes several values to need updates? I would think it’d be inefficient to call this value repeatedly.

In reality, I’m using a grid that is much more dynamic, meaning, I don’t know the columns in the grid to utilize for this call (again, it was a simple example to show the issue). The data on the grid (for a single row) is being updated and I’d like to refresh just that row’s worth of data (without the columns being known). I’d rather not refresh the grid in its entirety, just that row.

Is that possible?

Thanks again,
Chuck

[chuckmParticipant]

FYI…looks like something happened to my sandbox so I updated it to show the functionality again. Please let me know if you see the issue.

Thanks,
Chuck

[chuckmParticipant]

Good afternoon!

Would you happen to have an estimated date for when the next patch with this bug fix will be available?

Thank you!
Chuck

[Author]

Posts