>>>So does using the suggestion to copy slice still work with the unmodified ng-grid.js ?
>>>
>>>If it does I'd tend to stick with that. Having ng-grid perform a deep watch is expensive and the mod will mean it will always be creating a copy even in situations where it is unnecessary.
>>>
>>>If you do need an app wide solution then maybe an alternative would be to use $watchCollection() instead of $watch() in ng-grid ? I'm no angular expert but I think that would be less expensive. I'm always wary of making changes to libraries like this - all to easy for a change that you make to impact other areas of the app using the same library - and also too likely that another developer updates the version without being aware of the mod.
>>>
>>>IAC, if you're trying the ng-grid mod then, since you have a source version, you can debug - check if the watch is firing when you expect, compare newVal/oldVal etc.
>>
>>UPDATE: Duh. Added a bit to my last post and replied to myself instead of updating :-{
>
>The copy doesn't work with the unmodified latest version either (I removed that last parameter). I am going to restore to the version we had prior to that and re-try.
>
>I undid my changes (reverted to old version of ng-grid), but yet grid refuses to show data :(
Trying things at random means you are just thrashing around. If something doesn't work then debug 'till you find out why - then look for the solution.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only