[mbombergerParticipant]

Thanks, Hristo. My intention is not to change the source code. That always scares me and opens another can of worms :). I’ll give that topic a look just in case there is a relation. My fallback to this will probably end up being setOptions.

I’ll send an email out. Just so I do not end up breaking the rules, am I allowed to paste Jqx source code into a support email? If I could, that would make things so much clearer I think. I am also aware of the Github repo. Does that accept tickets from the community?

Your time is much appreciated.

Mark

[mbombergerParticipant]

Hi Hristo,

No errors in the console. I am positive the data and fields are correct.

All properties are not updated again and again. For the vast majority of cases in the app so far, the configuration is set once, and when data changes, it updates the source. If anything in the configuration changes, it needs to ensure all properties are updated accordingly. Angular should handle which inputs actually changed (and it does). This is a generic component, meaning anyone can configure any set of properties, and they can change them at any time.

Here is an example of how the component may be used for some more context

<my-jqx-grid [loading$]="loading$"
              [config$]="gridConfig$"
              [data$]="expenses$"
              [noDataMessage]="'No Data Found'"></my-jqx-grid>

loading$, config$, and data$ are all observables that can be pushed to by any action (loading$ isn’t very interesting in this case). config$ represents the settings for the grid, data$ represents the data returned from the service call.

As I mentioned, through debugging, I found the issue is that the jqxGridComponent bails out of updating properties before it reaches the source property. It would work otherwise. I would paste the relevant code, but I am not sure if I will break the EULA since I’d need to post JqxGrid source code to demonstrate. Is there another medium in which I can show this? I can maybe see if I can put together a quick fiddle.

If I can avoid using the methods, that would be my preference. Otherwise, I would just use jQuery directly. At the moment, my workaround involves setting the source through the source method.

I forgot to mention that my app currently uses Angular 8.2.14.

Thank you for your time,
Mark

[mbombergerParticipant]

Anyone available to take a look? The workaround I need to use to get around this has some undesirable side effects

[Author]

Posts