All Answers

Hi Tobias,

Deploying the files as you would with a traditional HTML system is the right approach especially with complex widgets that use their own javascript loaders, relative resources in css, etc.

But to answer your original question, this is the correct way:

• Place the resources in /Resources or /Platform
• Uncomment the WisejResources attribute in AssemblyInfo
• Reference like this “resource.wx/[AssemblyName]/Namespace/file. i.e. “resource.wx/MyApp/MyApp.Resources.leaflet.js”.

See also https://docs.wisej.com/docs/concepts/embedded-resources.

The [AssemblyName] in the URL is optional. If you omit it, Wisej will look for the file in all assemblies with [assembly:WisejResources]. And you can always override embedded resources by deploying the same file structure on the server.

Additionally, Wisej has a way to “inject” the “resource.wx” also when using complex systems in order to make everything work as a single assembly (in some cases it’s impossible and you have to deploy the files).

There are many examples and extensions that you can use as a guide on GitHub.

See https://docs.wisej.com/examples/, https://docs.wisej.com/extensions/

HTH

It’s not possible in any browser. User interaction is required.

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.

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.

Kingsley,

this issue is logged as #2754 and we´re looking into it.

Best regards
Frank

Cannot reproduce. I get the correct count in ControlAdded and ControlRemoved events.

Set debug=false in web.config. The logged warnings are as intended, don’t indicate any problem with the theme.

can you explain what you mean and how to correct?

Hi Edmundo,

You can download the extension from GitHub by selecting the 1.5 branch.

Here’s a link: https://github.com/iceteagroup/wisej-extensions

Let me know if this helps.

Best regards,

Alaa

Hi Luca,

Thanks for the follow up.

We have 2 applications built using Wisej. When we review the browser console for the application that we have not recently changed there are no such console messages. If as you say the messages are a normal occurrence, why do we have them in one application and not the other?

Also, on further investigation we can see that our mixim does not render within the application that generates the warnings.

Thanks . . .

Those warnings are normal. Our theme system is rendered progressively, when a widget is first loaded the corresponding appearance keys are converted to css and cached in the browser. When it finds a child control, for example an icon in a split button, it looks for an appearance for the child control that can override the default. i.e. “button/icon” instead of “icon”.

Newtown is not our product. System.Data is Microsoft. In any case, the circular serialization error means that a class is self referencing at one point. This is not a Wisej issue.

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.

Hi,

It’s probable that you’re using Movable=true in the wrong place. Can you check please?

Best,
Alaa

Hi, two options:

1. MesssageBox.Show(“OK”, modal:false) (see all optional arguments). BUT: it doesn’t work as it should and I will log the bug. Additionally when modal is false it should not block the page.
2. Currently you can change the color of the modal mask to transparent, however since the MessageBox is always modal (see 1 above) it will always block until the bug is fixed.

To change the color:

1. By code: Application.Theme.Colors.modalMask = “red” (this changes the cached theme shared by all sessions).
2. In a mixin: Add /Themes/App.mixin.theme file like this {“colors”:{“modalMask:”red”}}.

This is the notification API

https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API/Using_the_Notifications_API

Doesn’t work on iOS and it’s extremely unclear if it even works anywhere else.

We support push notifications with the Wisej native mobile packages available to Technology Partners. In alternative you can can use PhoneGap (Apache Cordova). Either way you have to host your notification server. In other words, it’s not easy.