If you are using Servoy 5.2+ you will need this version.
If you installed the v2.0 you must update to this version which fixes a major bug with the processFunction being called in a wrong Thread where some calls were failing (databaseManager calls notably).
I worked very hard to definitely fix the cancel call which was done AFTER the process itself was finished (!) in the web client, using a combination of Ajax direct call, Server plugin, RMI service and Servlet service in Web client.
Hi,
is there a chance that the “databaseManager call problem” fix will be backported to version 1.0?
I’m stuck with 4.1.7 and that issue gave me more than one headache.
It is not possible to change the display while the busy plugin blocks the display, that’s the whole point!
But please open a feature request on the ServoyForge project and I’ll see if I can add a mechanism to change the text message, although I’m not sure that this will be possible in web client.
Does changing the display also mean: opening a form in dialog? Is that the reason why plugins.file.writeFile() inside the busy block does not work correct?
In webclient writeFile shows a file selection dialog for entering the place where the downloaded file will be stored.
Exactly. The display is blocked and nothing can happen between the server (where the method is executed) and the browser until the end or cancellation of the process.
I am successfully using the v2.1.4 in Web Client. However, sometimes when a process starts, I just get the usual Servoy “Loading…” indicator instead of the busy screen. Any ideas as to why? This is even for processes that are 30 seconds or longer.
Please open a case at the ServoyForge project issue tracker, with precise explanation of your environment (Servoy version, Plugin version, Browser version), and if possible a sample solution.