Servoy 2025.6.0

Announcements
21

Is the plugins.dialogs module broke or am I doing something wrong?

var thePressedButton = plugins.dialogs.showErrorDialog('Title1', 'Value not allowed','OK', 'Cancel');
application.output('Title1 ' + thePressedButton);
var thePressedButton2 = plugins.dialogs.showErrorDialog('Title2', 'Value not allowed','OK', 'Cancel');
application.output('Title2 ' + thePressedButton2);

When this logic is executed the Title1 output is displayed immediately (execution doesn’t wait for dialog to return), and the Title2 dialog works correctly waiting for the response before continuing on with output statement.

I didn’t see anything in the release docs regarding the dialogs plugin. Is this a bug or do we need to make this call different now?

22

This i can’t reproduce that seems to work fine for me

23

this one i can reproduce, but this needs to have a deeper look, the button shows a different kind of initialization of the properties and because of that the enabled property itself is initialized with false which shouldn’t happen.

24

ok i did find a way to fix this to not influence the value (enabled) when it is not initialized yet (the enabledDataprovider)

25

I did some more testing and I believe this is what is causing it. Please try this:

controller.focusFirstField();
	
var thePressedButton = plugins.dialogs.showErrorDialog('Title1', 'Value not allowed','OK', 'Cancel');
application.output('Title1 ' + thePressedButton);
var thePressedButton2 = plugins.dialogs.showErrorDialog('Title2', 'Value not allowed','OK', 'Cancel');
application.output('Title2 ' + thePressedButton2);
26

yes that seems to cause it for some reason are the 2 calls where the first one doesn’t need to wait on will return directly the call of the second one where it should have been waited on

not sure why that is, can you create a case for this?

a quick fix for this would be a application.updateUI() call just before the show()

27

Created case SERVOY-230.