Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I am wondering if anyone else has tried out Qlik Sense on a Surface Pro?
I have just installed it and it seems to have trouble recognising keyboard input. Neither the Type Cover or the onscreen keyboard work within the application.
Hi Michael,
I will check internally and get back to you.
Regards,
Erik
Qlik Sense workings perfectly fine on my Microsoft Surface Pro ... onscreen keyboard, Type Cover and Touch Cover...
Installed on my Surface Pro running Windows 8.1. Works well with my Type Cover keypad.
Maybe it is just a glitch on mine.
For reference, I'm using a Pro 2.
I too was having issues with a Surface machine and IE with Qlik. I've found that I can not scroll in List Boxes or Chart Objects (but can make sections if it is viewable). Additionally, List Box values are conflicting that should not and do not on other devices/broswers that are based on set expressions for Time (Order vs Ship).
However, I've loaded Chrome, and all functionality works, but requires a little getting used to either using the mouse pad or swipe/touch.
Actually the newly release QlikView 11.2 SR11 has this not in it's Release Notes on page 4:
1.1.5 Support for Internet Explorer Touch
Touch mode on tablets or hybrid computers with Internet Explorer should now have the same
functionality as Safari and Chrome.
Actually it didn't work fine - I only thought so. ...
Michael (and others)
I too have Sense Desktop running on a Surface Pro 3, and I am seeing different behaviour between this machine and my 2 year old Sony Vaio. In the script editor the tab key behaves very differently: on the Vaio it indents the script, but on the Surface Pro it moves focus to elsewhere in the window - this means that if I want to indent script I either need to type four space characters, or take my hands off the keyboard and click the indent script button. The other most noticeable difference is that I am getting no type-ahead help at all in either the script editor or the expression editor on the Surface Pro.
Does anyone know if there are any settings anywhere (either within Sense or in the Windows settings) that I could tweak to change this behaviour?
I also see different behaviour when I right click on objects in the user interface, but I am assuming that this is because the Surface Pro has a touch screen, while the Vaio doesn't.
I am running Windows 8.1 and Sense version 2.0.1 on both my Vaio and my Surface Pro.
thanks
Brian
I am also having the same problem on Surface Pro 3 using Windows 10.