Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts

  • pablodg
    Participant

    Any updates on this? It is really pointless to have virtual scrollbar having to query data on every click.


    pablodg
    Participant

    Peter, a person cannot be good at everything. You may be good at coding, but for writing… you have to define concepts using different words than the concept itself.

    ‘Updatebound rebinds’ does not tell much. Reading this topic, it became clear to me that even if you coded the component, there are many many people more adequate than you for a clear answer. Probably any student for journalism, literature or related can do better. Actually, in my experience, being the author puts you in the worst position to imagine how a developer see, use or understand you components and words. You are the best for bug fixing, but maybe too far from user perspective.

    The samples of the components (and the components) are magnificent. The documentation is not as good, and I agree that if we are here, we’re not understanding the documentation.

    About this thread, if you have to change ‘source’ instead of calling updatebounddata (when modified the url), the whole thing is confusing. Actually, the whole ‘adapter’, ‘source’, and ‘source.data’ is tricky. Maybe different having adapter classes, like JsonAdater, ArrayAdaper, etc. (with properties, but not source) for each adapter strategy would be clearer.

    By the way, it would be nice if you could tell what refresh does, if updatebounddata internally calls refresh, and what rebind means in the context of your component. In my case, I update the data of an array and the rows do not show no matter I do updatebounddata or refreshbounddata.


    pablodg
    Participant

    Actually the real scenario is much more complex. I invested time in isolating the error in jseditor.io, as I though that was quite convenient for you to see the bug. Many of your customers can fall into that bug, and you have it isolated here.

    As Chrome allows you to put breakpoints, and you could look at it using the non-minified sources of the Grid (just replace the type=”text/javascript” src=”https://www.aacademica.org/js/jqwidgets-ver5.7.2/jqwidgets/jqxcore.js lines), I imagined (and I still think) that messy should not be a problem if you want to solve the bug.

    Thanks anyway for your time, PDG>

Viewing 3 posts - 1 through 3 (of 3 total)