[christian.folie@oebb.atParticipant]

Hello Peter,

We found out that our touchmonitor is not recognized as touchdevice by the widget:
$.jqx.mobile.isTouchDevice() returns false
As far as we understand, this is caused by the widget discerning touch and no-touch by checking the browser used by the device.
Since our touchmonitor uses the standard desktop version of chrome it is falsely labeled as no-touch.

Our Workaround:
Modernizr correctly labels our monitor as “touch” and dependant on that information we can set “$.jqx.mobile.touchDevice = true” in document.ready.
After doing that touch controls work as expected on the monitor.
We noticed that once touch is enabled this way, the mouse can no longer interact with the windows.
This is fine with us as the product is meant to be controlled by touch only.

If there is any further information to this subject it would be appreciated.
We would also like to suggest updating your touch-device recognition, as this seems to be the root of the problem.

Best Regards,
Christian

[christian.folie@oebb.atParticipant]

Since I cannot edit the OP anymore and I wanted to clearify:

The mobile Demos have the same behaviour.

mobile demo embedded
-> Chrome emulated touch works. Touchmonitor doesn’t work.

mobile demo not embedded
-> Neither emulated touch nor touchmonitor work.

[christian.folie@oebb.atParticipant]

Thanks a lot, this fixes our problem!

[christian.folie@oebb.atParticipant]

Hello Dimitar,

We do not expect the div to appear as window before clicking openFloating.
Our issue is the oppacity of the window after spawning and moving it. It looks just like it should when you drag the window, but the DragEnd seems to be missing, so the opacity stays.

The events are not needed, but we would like to open dockable windows outside of the docking area.

Best Regards

[christian.folie@oebb.atParticipant]

Hey,

We have the same requirement for our product:
Open a window outside of the dock but be able to dock it afterwards.

Bentwonk said

I tried spawning the window as default, and then moving it, but it did not move.

We made a jsFiddle where we managed to spawn and then move the window, however it appears to stay in the “drag-mode”.
After manually moving it, everything behaves as expected.
Can we fix this behaviour or is there another way to do this by now?

Best Regards,
Christian

[christian.folie@oebb.atParticipant]

Is there any new information regarding this issue?

I have the same problem in a virtual grid. The user presses either the cursor keys up/down or the page up/down. The gird performs usually one request, then looses the focus.
It seems to work with normal paging. At first I thought the autoshowloadelement setting might cause the focus to disapear, but disabling it did not help!

Thanks!

[Author]

Posts