jQWidgets Forums
Forum Replies Created
-
Author
-
January 7, 2014 at 3:41 pm in reply to: Beforeprocessing is not firing in jqxGrid. Beforeprocessing is not firing in jqxGrid. #47391
Hey Peter,
I also wanted to point out that there isn’t documentation regarding the
beforeprocessing
callback at http://www.jqwidgets.com/jquery-widgets-documentation/documentation/jqxdataadapter/jquery-data-adapter.htm or http://www.jqwidgets.com/jquery-widgets-demo/documentation/jqxdataadapter/jqxdataadapter-api.htmCheers,
– Joe
January 6, 2014 at 8:34 pm in reply to: updaterow & cellvaluechanged always triggered when displayfield specified. updaterow & cellvaluechanged always triggered when displayfield specified. #47352Awesome! Thanks
January 6, 2014 at 8:26 pm in reply to: updaterow & cellvaluechanged always triggered when displayfield specified. updaterow & cellvaluechanged always triggered when displayfield specified. #47350Hey Peter, yes, that is correct.
My point is when making the comparison to determine if the cell value has changed, null should be treated as an empty string. The current implementation treats them differently and triggers an update.
January 6, 2014 at 8:08 pm in reply to: Grid editor widgets are not destroyed after cell editing. Grid editor widgets are not destroyed after cell editing. #47347Hey Peter,
Yes, this is for custom editors. Is there an event that will give me access to the editor after editing is done so I can cleanup? I can’t seem to find any in the documentation.
Cheers,
– Joe
January 6, 2014 at 8:07 pm in reply to: updaterow & cellvaluechanged always triggered when displayfield specified. updaterow & cellvaluechanged always triggered when displayfield specified. #47344Hey Peter,
You will notice though that for Item 1 count, the value is null. When you exit editing mode, the grid thinks the value has changed to an empty string. Even though the underlying value is null, it should be treated the same as an empty string. If you put the Item 1 count back into editing mode and exit, you will notice the updaterow/cellvaluechanged didn’t trigger because the grid already updated the value to an empty string instead of null.
– Joe
January 6, 2014 at 7:42 pm in reply to: updaterow & cellvaluechanged always triggered when displayfield specified. updaterow & cellvaluechanged always triggered when displayfield specified. #47334Hey Peter,
I should also point out that the events are triggered when the cell value is null.
Follow the steps for the last reproduce step: http://jsfiddle.net/jgornick/7WCks/
January 6, 2014 at 5:48 pm in reply to: Grid row disable edit and loading indicator. Grid row disable edit and loading indicator. #47323Hey Peter,
My 2 cents:
I don’t think you should look at custom events triggered from the grid as “grid events” vs “browser events”. Any event triggered from the grid (DOM or custom) should have the same abilities as the declarative event callbacks.
For example
grid .jqxGrid({ // ... columns: [ { text: 'Name', datafield: 'name', cellbeginedit: function(...args) { // prevent default behavior return false; } } ], // ... }) .on('cellbeginedit', function(e) { // prevent default behavior e.preventDefault(); });
The point is this is “one event” that is triggered multiple ways. You should be able to perform the same actions for both handlers. Even though you are triggering events through jQuery doesn’t make them “browser events”. The grid becomes an event emitter and the type of event determines if it’s a custom or DOM event.
Cheers,
– Joe
January 6, 2014 at 4:14 pm in reply to: Grid row disable edit and loading indicator. Grid row disable edit and loading indicator. #47321Bump.
January 3, 2014 at 8:46 pm in reply to: Column displayfield not reset after dataAdapter commit(false). Column displayfield not reset after dataAdapter commit(false). #47219Awesome! Thanks Peter.
January 3, 2014 at 6:05 pm in reply to: Column displayfield not reset after dataAdapter commit(false). Column displayfield not reset after dataAdapter commit(false). #47206Hi Peter,
Here’s a link to the failing test: http://jsfiddle.net/jgornick/8w4bG/
January 3, 2014 at 5:36 pm in reply to: Add event that is triggered after updaterow commit is called. Add event that is triggered after updaterow commit is called. #47201Hey Peter,
Thanks for the prompt response. I don’t think it’s a matter of “throwing exceptions” but a matter of better handling asynchronous operations, and more importantly, error scenarios. Unless I’m missing something, the operations provided as part of the grid and dataAdapter interaction are very synchronous.
I’m currently evaluating your product for purchase and am finding that handling of error scenarios are not well documented and asynchronous request handling isn’t well supported either. Is there something I can do to more clearly state the issue I’m having?
Cheers,
– Joe
January 2, 2014 at 11:47 pm in reply to: Grid row disable edit and loading indicator. Grid row disable edit and loading indicator. #47161Hey Peter,
The thing about using cellsrenderer is that it is called immediately after updaterow, but before the request finished. This means that I couldn’t use it to put a row in “disabled” while the update request is processing. The other thing about cellsrenderer is it’s called too often and on all of the rows in the grid. This is a little wasteful for my scenario.
What I’m looking to do is before updaterow is called (cellendedit) put a div over the row currently being edited and prevent all editable cells from being edited. Then, after the updaterow is “committed” (cellvaluechanged), remove the div and allow the cells to be edited again.
In the example you posted, there is a way to disable cell editing by adding a cellbeginedit handler to each of the columns in the grid. Then in the handler, return false when the row is in a list of non-editable rows.
Just as a test, I’m trying to disable all cell editing in a grid by:
grid.on('cellbeginedit', function(e) { e.preventDefault(); e.stopPropagation(); return false; });
The event fires properly, however, it seems the logic is not respecting the preventDefault, stopPropagation or return false in the event handler. Can you confirm this behavior?
Cheers,
– Joe
January 2, 2014 at 11:13 pm in reply to: Update search results to only show titles of related topics Update search results to only show titles of related topics #47159Thanks!
January 2, 2014 at 9:29 pm in reply to: Grid row disable edit and loading indicator. Grid row disable edit and loading indicator. #47151Hi Peter,
Is there a way to do this runtime? The example provide only shows how to disable rows after the grid renders. I’m looking for more of a dynamic approach rather than static.
Cheers,
– Joe
-
AuthorPosts