U++ forum: Welcome to the forum

Close() callback not conditioned in a dialog [message #6347]

Tue, 07 November 2006 21:28

forlano
Messages: 1207
Registered: March 2006
Location: Italy

Senior Contributor

Hello,

in some dialog containing for example an edit widget I perform a control to avoid if it is empty. So I force the flag Notnull in the designer for that widget. The dialog has then an OK and Close buttons.
The problem: when the user press Close o whatever button that performs a Close() action the dialog does not close if the user do not enter some weird thing in the edit widget. So the widget has priority on the close callback.
I think that the closure of the dialog connected with the Close() callback should be immediate and irrespective of the condition of the others widgets (not null for example), because these eventual data will lost be in any case. It should be responsability of the programmer eventually confirm the closure of the dialog.
This is particularly annoying if the dialog contains many ctrls with not null flag activated.
Of course this problem can be bypassed removing the Notnull flag and performing a control on each widget but this seems to me not natural if the notnull method exists.

Luigi

[Updated on: Tue, 07 November 2006 21:29]

Report message to a moderator