[bigman73Participant]

I’m facing the same issue but the suggested workaround doesn’t work. The demo jsFiddle shows two console traces (tested on Chrome).
It seems that the identical event is fired twice.

I solved it, as a workaround, but comparing the event time stamp to the last time stamp. keep a variable for the last time stamp.
Ugly but works.

[bigman73Participant]

I have a similar problem but the jqxGrid is placed (with other jqxGrid controls) inside a div which in inside another container (but not from jqxwidgets).
Once I scroll down the top level container the jqxGrid selections get corrupted – they take into account the offset of the vertical scroll position of the container, which is incorrect, and the hover proves it. The selected row is above the actual mouse position, depending on the container’s vertical scroll bar position.

Please advise.

[bigman73Participant]

Hi,
I tried all the options above without success.
Is there a working example that shows how to have a multi-line editor in a jqxGrid

Thanks.

[bigman73Participant]

UPDATE:
I got it to work with –

var element = $('<input type="text" id="propertygridinput"/>');
                editor.append(element);
                editor.jqxInput({ height: height, width: width });

[bigman73Participant]

Hi Peter,
I’m evaluating usage of jQWidgets and a possible purchase of a license.
Conflicts with the popular D3JS library is a major concern to me.
In regards to the specific and very clear reproduction of the issue presented above, using jsfiddle, it looks like adding jqwidgets affects D3JS, not d3js affecting jqwidgets.
“If that libary handles events and prevents them to be handled from other plugins,”
It seems that once jqwidgets is disabled the drag drop events return to function with D3JS, which suggests that the problem might be jqWidgets blocking the event.

Could you look at that problem and provide an explanation?

Thanks
Yuval

[Author]

Posts