Reporting Progress

0
0

Hello,

I downloaded the progress sample from https://wisej.com/blog/progress/

The program isn’t behaving as described, it doesn’t report progress unless I move the window around using the mouse.

For each window move the window is upgraded, but not it it’s sitting.

I’m using latest build 1.4.59 on Win7 and VS2015.

Is it the same effect on your side ?

 

Regards.

  • You must to post comments
0
0

We have added an option to poll the server at a configurable interval automatically when a WebSocket connection is not established and the application needs to update the client in a background task. It’s basically a WebSocket emulation without using long polling which blocks a thread.

  • Eric Mathay
    Hi, That’s what I name a proactive solution to bring your technology to everyone, without having technology barriers or technical compromises required. Better than forcing people in one direction. Having it built-in without worry about it is very nice.
  • You must to post comments
0
0

Hi Luca,

I checked Frank’s recommendationabout websocket, and found it’s enabled on my Server, but the sample still made partial reporting.

But using the sample “Wisej.BackgroundTasks2”,  it was reporting properly.

Now I understand why I couldn’t find why 🙂

So that It effectively must be the ProgressCircle.

 

  • You must to post comments
0
0

Yes it’s a regression related to the ProgressCircle component and websocket.

  • You must to post comments
0
0

Looks like we may have a regression in dev build .59 regarding out of sync updates.

  • You must to post comments
0
0

Hi Eric,

Winsocket is not enabled by default on Windows Server (any version). So you need to install it on your Windows 2012 server:

You have to add it using windows features: http://danielhindrikes.se/windows-8/enable-websocket-protocol-in-iis/

Hope that helps.

Best regards
Frank

  • You must to post comments
0
0

Hi Eric,

you need to enable WebSockets. Can you please check with e.g. Chrome Console (F12), then type Wisej.Core.request
It should show something like this:

{loaderTimeout: 2000, loaderTimerId: 0, loaderVisible: false, webSocket: WebSocket, useWebSocket: true, …}

Hope that helps.

Best regards
Frank

  • Eric Mathay
    Hi Frank, You are right about websocket (I was testing on IIS Express under Win7, and as Win7 doesn’t support Websocket …). I tried it deployed to a Win2012 Server. At start, the progressbar is advancing and the 10% are reported. After this the report stops, until you click the window. After each click, it will report until the percentage update of that step, then nothing more. You have to click again to get the currently background running update. Cancelling the task is working. Selecting block execution will update until 10% then nothing more, and because the interface is properly showing the wait cursor, you have to wait till end of execution. Any idea ?
  • You must to post comments
Showing 6 results
Your Answer

Please first to submit.