[WB26] - Auto refresh a page

Hi All

How do I set a page to auto refresh every N seconds so that it can reflect new data updates on the server?

I have looked at Compatibility: Update browser data from the server every n-seconds but the page does not seem to refresh and not sure what code it runs ?

You can do it for instance using TIMER and AJAXEXECUTE

You can find one example provided with webdev for one chat app just take a look at it.

As always this can be done in several ways, check this one to see it's OK for you.

Regards

Paulo Oliveira

Paulo

OK, I see the way. Create a procedure and use a procedure timer to refresh the page contents. I thought there might be a setting for the page itself that one could just click on/off but OK, will investigate. Thanks.



Edited 1 time(s). Last edit at 07/29/2021 06:38PM by JP.

Hi Paulo

I have been trying various things but cannot get it to work.

1) I looked into AjaxExecute() and when I use this to call a server procedure from browser code to get the new data that works. And in the browser I can update the page controls with the new data.

2) But I cannot see how to do this a continuous loop so that the data is refreshed every N-seconds

3) I cannot find the chat app example in WinDev 26 either.

TIA

The example was in V18.

To do it every X seconds use one TIMER in browser code.

Regards

Paulo Oliveira

Paulo

Thanks. I have it working with the Timer() function. So I have:

1) In the Page Load - Onload Browser Event I use Timer() to call a browser procedure.

2) The Browser procedure then calls a server function using AjaxExecute to retrieve the new data.

3) Then the Browser procedure updates the specific controls required with the new data.

Does that make sense? It seems to work

Hi all

Ideally, you do something like this with websockets...
Also a standard feature of V26.

Cheers

Peter H.



Edited 1 time(s). Last edit at 07/31/2021 03:50PM by PeHoBe.

it is the correct logic BUT

1. you should use ajaxexecuteasynchronous to do the refresh, in order to avoid blocking your customer during the dialog with the server (very fast in test, not so much in production)
2. you should test on the server side if there is anything new and decide if you do a refresh or not, as you do not want to refresh a page with the exact same data.

Argus

Yes, agree and have done those 2 things. Thanks

Cheers