All Answers

I’m experiencing the same problem.  Project works fine on one computer.  On the other computer, the Theme does not load in the designer. But it loads at Runtime.

For some reason the designer still thinks my theme is is Blue-1, and not my modified Blue-1. I did a low level scan with Process Explorer and it didn’t even seem like my modified theme was being hit when I opened a form in the VS designer (2017 Community, latest version)

Set AllowHtml to true then you can show anything in the cell. A simple progress bar would:

<div style=”height:100%;width:{value}px; color:red”></div>

Where {value} is the progress bar width as 100/width*value.

The error seems to be coming from jQuery and Asp.Net Api. Wisej doesnt generate 405 errors. Make sure the the [WebMethod] attribute you are using for Asp.Net is NOT the Wisej WebMethod attributed because Asp.Net doesn’t recognize it. Also, if you upload a small test case we can take a look.

While this  (WJ-9117) still appears fixed, I have another issue now. I am getting it in both 1.5.16 and 1.5.19…. it is with MouseClick and not with MapClick.  A tap on the screen punches “through” a MenuItem , and then registers on the map (a marker’s InfoWindow HREF link), firing a MouseClick event.

The MenuItem click code fires first. Because that code changes objects that the MouseClick event later refers to, it throws an exception when the object is no longer available.  The MouseClick event should never fire in this scenario.

I’m emailing you a video of it now.

thanks

Andrew

Hi Andi,

Please clarify some questions.

1. The other computers you mention are also running Wisej 1.5.17?
2. The exact same themes files that mis-behave on your computer, do they behave correctly on other computers?

Hi Andi,

If I understood correctly, your theme files were ok under Wisej 1.5.4.

Since this Wisej release, there were updates to the theme files. Most probably the theme files you are using miss some settings.

Please note that when you build a mixin theme file, you don’t need to remove anything the main theme file, as the settings in the mixin file verwrite the settings in the main theme file.

Please try to use one of the default theme files.

Hi Andi,

Running the installer should result in a proper instalation. There are a number a things you can try:

1. Close Visual Studio and run the installer again and select repair.
2. Restart the computer and open ThemeBuilder before opening Visual Studio.
3. If you are  opening an existing project, turn on visibility of invisble files and delete the folder .vs

It this doesn’t solve the issue, please report back.

As an addendum, I moved bits from our theme to a mixin.
The bits I moved are ok.
Whilst I could accept it is all down to a corrupt .theme file, I don’t understand why it would work at runtime but not designtime if the .theme file was invalid.

So I have a way forward, but it worries me as to why the original file is not working in the designer still.

Roni,

The fix will be published soon but I don’t have a estimated date.

If you have several companies stopped, you can try to use some previous version of Wisej.

HTH

Hi Ricardo,

I can’t reproduce the behaviour you describe: after I instanciate a window when I call window.ShowDialog() the form shows on the spot.

In the json file, you can use loaderTimeout to set the Timeout before the appearance of the Ajax loader in milliseconds. Default: 2000.

Please note there are several Wisej-Examples available on our GitHub repository.

Right, I am wondering about the best practices to configure cache on an IIS web server to work with WiseJ.

For example, I had configured “HTTP Output caching” under IIS Manager by setting file types *.css *.js, etc, but I still had static assets (domain.io/Resources/Javascript/*.js etc) that were not being cached, but I fixed that by adding

<staticContent>
<clientCache cacheControlMode=”UseMaxAge” cacheControlMaxAge=”30.00:00:00″ />
</staticContent>

to my web.config file. But it seems this is not right use of etag?

I still now have these WiseJ managed resources that seem to never be cached no matter what — based on your explanation I am guessing this is not the expected behavior  (via https://www.giftofspeed.com)

https://domain.io/wisej.wx
https://domain.io/resource.wx/init?_sc=1537809853726
https://domain.io/resource.wx/wisej.min.css?v=1.5.19.0
https://domain.io/resource.wx/Wisej.Web/qx.min.js?v=1.5.19.0
https://domain.io/resource.wx/wisej.min.js?v=1.5.19.0

So it seems the browser will be forced to fetch the bootstrapper everytime (confirmed in network tab and Lighthouse). Per an earlier email you told me to exclude the .wx extension from “HTTP Output Caching”. In an earlier thread (https://wisej.com/support/question/static-content-can-be-cached) you said these files were cached but I can’t get it to work.

About Service Workers — -I know WiseJ doesn’t use Service Workers… the WebWorker example is not a service worker in the same sense as a PWA service worker as indicated by the guide. I’ve read the guide but had trouble implementing it.  The issues are complicated by server cache.

Wisej doesn’t handle the browser cache. I don’t think there is a way to affect the browser cache in javascript. For the server side and only for Wisej managed resources we generetae ETags. There is nothing you need to do to manage that.

For all resources not managed by Wisej, which is every URL not ending with .wx, the caching method is managed by the web server.

Wisej doesn’t use service workers. There is a downloadable service worker extension and example in github. For a detailed service worker guide I found this: https://developers.google.com/web/fundamentals/primers/service-workers/ but it’s entirely out of the wisej scope.

The rendering is for individual controls and saved in memory. The number of controls affects the initial rendering. It also depends on the speed of the dev machine. Composite custom controls are rendered as a single control.

IE11 is faster than Chromium for in memory rendering.

Are you using the Wisej session from the api call?

Hello,

I’m getting the same issue. Click events don’t seem to work in windows 10 phone.

Version 1.5.17

Thanks Tiago,

It’s… weird…

I’ve made the test directly in the server, and it also worked ok (on ie11)!

Even comparing the settings between the two systems, all seems similar.

If the problem is only with my machine, that’s ok -i use edge to debug;  but i will try to use other machines to get more data…

By the way, the “problematic” setup is in a pc and a laptop, both with windows 10.

Thanks again!

Yes but the problem remains, see the picture

Hi Nikos,

Following the thread you referred, did you try to restart VS in admin mode?

Hi Johann,

I contacted you privately.