jQWidgets Forums

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 16 total)
  • Author
    Posts
  • in reply to: jqxGrid addrow selection bug jqxGrid addrow selection bug #102232

    Llorx
    Participant

    Still not fixed? I had to fix this by myself modifying the source code.

    in reply to: Bug: Another memory leak Bug: Another memory leak #102231

    Llorx
    Participant

    Of course you have a similar forum topic. Is my other post which I state in this post (Guess you didn’t read it :-() that I cannot modify the title with another different memory leak :-/


    Llorx
    Participant

    So, when displayfield is set, datafield is used for nothing? Then what’s the reason to have a datafield?

    Wouldn’t it be more logical to make the “internal data workings” with the datafield and the displayfield used only for display? (As its name states).

    in reply to: Bug: Another memory leak Bug: Another memory leak #93868

    Llorx
    Participant

    I fixed the bug by modifying the source code, as I needed to get this fixed ASAP, but EULA don’t allows me to post code here :-/

    in reply to: scroll event? scroll event? #92777

    Llorx
    Participant

    Note that this event will be removed on each render because of the internal _removeHandlers method, so you will need to attach it again on each “rendered” callback:

    $("#grid").jqxGrid({rendered: attach});
    
    var scbar = $("#grid").jqxGrid("hScrollBar"); // Horizontal scrollbar. Verical one is vScrollBar
    scbar.jqxScrollBar("_triggervaluechanged", true);
    
    function attach() {
        scbar.off("valueChanged").on("valueChanged", function() {
            console.log("yay!");
        });
    }
    attach();
    in reply to: Get Cell Element Get Cell Element #90211

    Llorx
    Participant

    So no reply to the last direct question? Is important for us to have access to the cell HTML element on click. Not to work with it, maybe to do whatever we want, like show a tooltip near it instead than mouse location.


    Llorx
    Participant

    Notice that I’m not talking about resizing when you have the dropdown open. I’m partially fine about that. I’m talking about opening the dropdown after resizing. Is almost impossible to open it on first click.

    Following the steps:
    – Click on resize button
    – Click on the third column to edit the value
    – Notice how the dropdown appeared for a frame and then disappeared, without opening


    Llorx
    Participant

    I doubt that the bugs I mentioned are on design. Have you tried the fiddle?

    I repeat: When you resize, you cannot open the editor, because it appears and disappears instantly, being unable to open it at first click: https://goo.gl/kmcmY3

    This only happens if you have dynamic width (100%) but not if you have a fixed width, so yes, I doubt a lot that is a feature but a bug.

    Also, when it finally appears at first click after resize (I repeat, at first click after resize, happening only 1% of the times you click), it don’t save the changes. When you are on, let’s say, 3, and you change to 4, when you lose focus it returns to 3 again.

    Really, I hoped that this time I didn’t receive the same “seems a bug but is a feature”, but I was wrong :-/


    Llorx
    Participant

    Yeah, that’s what I did. .trigger("rowunselect"); after “clearselection” and done.


    Llorx
    Participant

    Yes, when I edit a cell, I modify his boundata directly, delete his “_cellscache” entry manually and call “_renderrows”, which refills the empty or different “_cellscache” items only, so I don’t need to call “render”, “setcellvalue” or “updaterow”.

    Now It works like a charm, but is a bit hackish as I’m accesing private elements that maybe can change in the next updates.

    in reply to: scroll event? scroll event? #87774

    Llorx
    Participant

    Created another small hack, accessing internal scrollbar, that will perform better than mousemove or setInterval:

    var scbar = $("#grid").jqxGrid("hScrollBar"); // Horizontal scrollbar. Verical one is vScrollBar
    scbar.jqxScrollBar("_triggervaluechanged", true);
    scbar.on("valueChanged", function() {
        console.log("yay!");
    });
    in reply to: scroll event? scroll event? #87765

    Llorx
    Participant

    Seriously we have to do such bad performing hacks to detect a common event?


    Llorx
    Participant

    Indeed


    Llorx
    Participant

    But, if jqWidgets size control is inconsistent because of all the reasons we stated above, how can I avoid overriding content-box but have a real 100% size instead of a 100% + 2 pixels size because of borders?

    Because removing the border leads to bugs, like I said above too.


    Llorx
    Participant

    PD: A new bug regarding borders (but I think that not content-box), for example. I updated jqWidgets and that added a border around jqxTree. I don’t want any border if I don’t specify it, so remove it with:

    .jqx-tree {
    border: none!important;
    }

    Now, the tree don’t renders wll. Renders with heigh 0. If I remove the “border: none” directly in Chrome devtools, it renders visible again.

Viewing 15 posts - 1 through 15 (of 16 total)