[shimmorilParticipant]

Thanks for the response Christopher. I don’t think that customizing the filter menu will help us any, since we need to keep all the potential options. We’ll investigate further on our end.

[shimmorilParticipant]

I have read all of your posts, and not one says that you’ve been able to replicate the bug I reported. Stating that “in case something is changed” means nothing – I know something has changed because functionality that used to work, no longer does. That’s the entire reason I’m contacting you. Telling me that your next release is in April, again, does me no good unless I know that you’ve replicated the bug and will be implementing a fix in that release. This is a simple yes or no question – have you been able to replicate the bug?

[shimmorilParticipant]

Your previous response says nothing about being able or unable to duplicate the reported bug – which again, to be clear, is the issue of hitting Enter after typing into the grid filter no longer runs the filter. All I want to know is that you’ve verified that there is a bug, and will be fixing it in a future release. This is not a difficult or unreasonable request and I don’t know why you’re stonewalling me.

[shimmorilParticipant]

Yes, thanks I was already planing on not using the latest version that causes hundreds of javascript errors just by typing. My original question still stands – have you been able to duplicate the bug (the original issue, where you can no longer use Enter after typing into the filters), and if so, do you have an estimate as to when it will be fixed?

[shimmorilParticipant]

I really need a response from someone regarding this issue. As mentioned multiple times, this is causing a large volume of support tickets for us, since it’s functionality that’s been available for years that has suddenly disappeared. Please let me know if you were able to recreate the bug, and if so, an approximate period for when it will be fixed.

[shimmorilParticipant]

Does that mean you were able to replicate the issue? Is a fix actually scheduled for the April release? We’ve got clients asking every day why hitting enter no longer works for filtering, which is obviously a big time/resource drain for us.

[shimmorilParticipant]

Any updates on this issue?

[shimmorilParticipant]

Thanks Peter. Please let me know if you’re unable to reproduce – I’ve been able to get the error consistently in Firefox, Chrome and IE.

[shimmorilParticipant]

Thanks for the response Peter. Re this:

you cannot achieve what you try to achieve with the current editor

Actually my original question was meant to determine if it is possible w/ our current editor – obviously that’s the least “expensive” option for us.

Yes, with cellbeginedit you can cancel cell editing. You can cancel it by setting a column’s editable property to false, too. This can be done dynamically through the “setcolumnproperty” method.

I’m not sure how cancelling editing after they’ve clicked helps me at all – my primary concern is that it would still visually appear to be editable, which would be confusing to the users. I’ve got the same concerns w/ the setcolumnproperty option – aside from having to loop through each row and update the property for each column (in the ready function I guess?), I’d still be left with cells that look editable, even if they’re not.

Utimately, what I’m looking for the the ability to display editable and uneditable rows differently – like we’re currently doing w/ the cellbeginedit vs the cellsrenderer by on a row-by-row basis, instead of the whole grid.

[shimmorilParticipant]

Sorry, I’m not following how that will help in my situation. For each row I need to check the value of a column in that row. If it’s 1, then other columns on that row are editable. If it’s 0, they’re not. In the example provided you’re just checking the row number and then setting a type of edit control, not actually preventing editing.

There also doesn’t appear to be a way to capture the change of value of a column, which is why we’re using cellbeginedit – I need to know if the value has changed in order to save the data.

[shimmorilParticipant]

Alright, thanks Dimitar.

[shimmorilParticipant]

Yes, I am aware of how to close the popup. My issue is that the error message has to be manually dismissed, which interrupts the workflow. If the cell is no longer failing validation, it should remove the error automatically.

[shimmorilParticipant]

Is there any way to have the error auto-dismiss after the text has been corrected? For instance, if I type 101 characters into the field, it give an error. So then I delete 2 or 3 characters (bringing me below the limit), but the error is still visible, and I have to click on it to dismiss it before I can continue working.

[shimmorilParticipant]

That looks great, thanks Dimitar.

[shimmorilParticipant]

Email sent to support.

[Author]

Posts