Taskbar StartButton behaviour on Tablet

0
0

Hi,

Strange behavior with the Desktop project when adding a Start Button to the taskbar.

I add a Javascript control to the Desktop and add an Appear Event to the JavascriptEvents Collection

this.resetUserBounds();

App.Desktop
    .getChildControl("taskbar")
    .getChildControl("shortcuts").add(this);

All is working fine when running on a PC, but once the code is run from a DELL Latitude 7212 Tablet, the StartButton needs to be clicked twice in a row to have it Perform it's Click.
The first click only selects the button, the second click executes the Click.
As soon as I remove the Appear Event, the Button stays on the Desktop and Performs properly.

If I try adding the script to the ClientEvents Collection, same effect.
I tried attaching to the button MouseClick, same effect.

Any idea about what could introduce this two step effect when on a tablet ?

Best Regards.
  • You must to post comments
0
0

Hi,

Find attached one of your old project, slightly modified.

I also have a 14 Mb video showing the twice Click effect in Firefox and the same project functional in Chrome, but it isn’t accepted to be uploaded (forbidden error message).

The appears is used to add the button to the Taskbar.

Firefox is 92.0  & Wisej is 2.2.58

Win10 64 Enterprise 1909(OS build 18363.1734), Pen & Touch : Touch support with 10 Touch Points.

Best Regards.

 

  • You must to post comments
0
0

Hi,

Find attached one of your old project, slightly modified.

I also have a 14 Mb video showing the twice Click effect in Firefox and the same project functional in Chrome, but it isn’t accepted to be uploaded (forbidden error message).

The appears is used to add the button to the Taskbar.

Firefox is 92.0  & Wisej is 2.2.58

Win10 64 Enterprise 1909(OS build 18363.1734), Pen & Touch : Touch support with 10 Touch Points.

Best Regards.

 

  • You must to post comments
0
0

Hi Frank, sorry for the delay, had no access to a test device.

It seems that :

The behaviour is depending if a mouse is connected or not. The device itself doesn’t play a role. With the tablet fitted with a mouse, same behaviour as on a desktop.

Without a mouse, what I can see from the console, is that the click is interpreted as a longtap.

So the console log WITH A MOUSE attached :

006469 qx.theme.manager.Appearance[21-0]: Missing appearance: button/label
006781 Wisej: Event id_5 {args:{…(4)}, id:id_5, type:focusin}
006783 Wisej: Event id_5 {args:{…(5)}, id:id_5, type:mousedown}
006788 qx.ui.core.queue.Manager: Flush Completed: 0 ms
006858 Wisej: Event id_5 {args:{…(4)}, id:id_5, type:execute}
006859 Wisej: Event id_5 {args:{…(5)}, id:id_5, type:tap}
006859 Wisej: Event id_5 {args:{…(5)}, id:id_5, type:mouseup}
006860 Wisej: Event id_5 {args:{…(5)}, id:id_5, type:click}
006933 Wisej: WebSocket Request 2
006942 Wisej: Process Response length: 6627
006943 Wisej: Process Actions count: 1
006944 Wisej: Process Action 2
006963 Wisej: Action Create created: 8
006963 Wisej: Process Action 5
006965 Wisej: Process Actions elapsed: 22 ms
006969 qx.theme.manager.Appearance[21-0]: Missing appearance: panel/pane/pane
006970 qx.theme.manager.Appearance[21-0]: Missing appearance: panel/popup
006971 qx.theme.manager.Appearance[21-0]: Missing appearance: button/label
006971 qx.theme.manager.Appearance[21-0]: Missing appearance: button/label
006972 qx.theme.manager.Appearance[21-0]: Missing appearance: button/label
006972 qx.theme.manager.Appearance[21-0]: Missing appearance: button/label
006973 qx.theme.manager.Appearance[21-0]: Missing appearance: button/label
006973 qx.theme.manager.Appearance[21-0]: Missing appearance: button/label
006973 qx.theme.manager.Appearance[21-0]: Missing appearance: button/label
006979 Wisej: Event id_8 {args:{…(1)}, id:id_8, type:resize}
006979 Wisej: Event id_8 {args:{…(1)}, id:id_8, type:popupMove}
006988 Wisej: Event id_8 {id:id_8, type:appear}
006990 qx.theme.manager.Appearance[21-0]: Missing appearance: panel/popup
006991 Wisej: Event id_8 {args:{…(1)}, id:id_8, type:popupMove}
006991 qx.ui.core.queue.Manager: Flush Completed: 23 ms
007003 qx.ui.core.queue.Manager: Flush Completed: 2 ms
007067 qx.theme.manager.Appearance[21-0]: Missing appearance: panel/popup

 

The console log WITHOUT A MOUSE :

1398435 qx.theme.manager.Appearance[21-0]: Missing appearance: button/label
1398439 qx.ui.core.queue.Manager: Flush Completed: 0 ms
1398462 Wisej: Event id_5 {args:{…(5)}, id:id_5, type:mousedown}
1398464 Wisej: Event id_5 {args:{…(5)}, id:id_5, type:mouseup}
1398626 Wisej: WebSocket Request 2
1398636 Wisej: Process Response length: 12
1398638 Wisej: Process Actions count: 0
1398648 Wisej: Process Action 0
1398649 Wisej: Process Actions elapsed: 11 ms
1398945 Wisej: Event id_5 {args:{…(5)}, id:id_5, type:longtap}
1398947 Wisej: Event id_3 {args:{…(6)}, id:id_3, type:longtap}
1399111 Wisej: WebSocket Request 2
1399121 Wisej: Process Response length: 12
1399123 Wisej: Process Actions count: 0
1399131 Wisej: Process Action 0
1399134 Wisej: Process Actions elapsed: 11 ms
1402308 Wisej: Event id_5 {args:{…(4)}, id:id_5, type:execute}
1402309 Wisej: Event id_5 {args:{…(5)}, id:id_5, type:tap}
1402310 qx.theme.manager.Appearance[21-0]: Missing appearance: button/label

Could this be the problem ? Creating a new Desktop App from the template does the same. Do you want me to provide one ?

Best Regards.

  • Eric Mathay
    Frank, just discovered that the problem is happening from Firefox. The Win10 internet explorer and the ‘New EDGE’, and Chrome are working properly. The longtap seems to be the problem. Tablet mode doesn’t play a role. Best Regards.
  • Luca (ITG)
    Can you please send a test case? I cannot reproduce with our http://demo.wisej.com/codeproject sample with the desktop and I didn’t understand what you are adding to the toolbar and what is the role of the “appear” event handler.
  • You must to post comments
0
0

Hi Eric,

any chance to set up a sample for us? For now it´s a bit unclear why you are using JavaScript directly to add the widget.
Also we don´t know yet where you´re adding the Appear handler.

You might want to check the console for any error:
Either use Application.ShowConsole = true in your application or hit Ctrl+F7 if you´re device has a keyboard.
In order to show the console, your application has to be deployed in debug mode.

Best regards
Frank

  • You must to post comments
Showing 4 results
Your Answer

Please first to submit.