Prev: fprintf problems
Next: serial communication
From: Samuele on 18 Jun 2010 08:35
hello,
i have a problem concerning the uiwait. I look at the forum and others webpages without finding any relevant information.

My problem is the following :
I have manually created a tabbed GUI with uitabpanel. In the interface there are several parameters that the user can configure. When parameters are selected, the user press the "run" button and before running the code i check the inserted parameters.
If parameters are wrong, i popup a message error with errordlg and i use uiwait to block the program till the user as pressed the ok button on the error dialog. But at this time a problem arises, if i move the error dialog box without pressing ok (on the error dialog) and i try to modify the parameters and press the run buttton in my interface this process can be executed.....I seem that the uiwait does not block my interface....
My question is the following : how can i block the GUI till the errordlg is not closed? (by block i mean that user cannot interract with my GUI)

Thank you, bests
Samuele
From: Walter Roberson on 18 Jun 2010 09:01
Samuele wrote:

> My problem is the following :
> I have manually created a tabbed GUI with uitabpanel. In the interface
> there are several parameters that the user can configure. When
> parameters are selected, the user press the "run" button and before
> running the code i check the inserted parameters. If parameters are
> wrong, i popup a message error with errordlg and i use uiwait to block
> the program till the user as pressed the ok button on the error dialog.
> But at this time a problem arises, if i move the error dialog box
> without pressing ok (on the error dialog) and i try to modify the
> parameters and press the run buttton in my interface this process can be
> executed.....I seem that the uiwait does not block my interface....
> My question is the following : how can i block the GUI till the errordlg
> is not closed? (by block i mean that user cannot interract with my GUI)

Use the 'modal' option of errordlg().

Usually in GUIs you would want to set the 'Enable' property of the Run
button to 'off' while you are doing a calculation, unless you
specifically designed the system to create multiple independent windows
for the various runs and you don't mind that the runs will interfere
with each other (that is, that only one of them can actually do
calculations at any one time, with the others being shut out of
continuing until the routine does the calculation allows interrupts by
doing a pause() or drawnow() or the like.)
From: Samuele on 18 Jun 2010 09:13
Walter Roberson <roberson(a)hushmail.com> wrote in message <S6KSn.83265$HG1.71884(a)newsfe21.iad>...
> Samuele wrote:
>
> > My problem is the following :
> > I have manually created a tabbed GUI with uitabpanel. In the interface
> > there are several parameters that the user can configure. When
> > parameters are selected, the user press the "run" button and before
> > running the code i check the inserted parameters. If parameters are
> > wrong, i popup a message error with errordlg and i use uiwait to block
> > the program till the user as pressed the ok button on the error dialog.
> > But at this time a problem arises, if i move the error dialog box
> > without pressing ok (on the error dialog) and i try to modify the
> > parameters and press the run buttton in my interface this process can be
> > executed.....I seem that the uiwait does not block my interface....
> > My question is the following : how can i block the GUI till the errordlg
> > is not closed? (by block i mean that user cannot interract with my GUI)
>
> Use the 'modal' option of errordlg().
>
> Usually in GUIs you would want to set the 'Enable' property of the Run
> button to 'off' while you are doing a calculation, unless you
> specifically designed the system to create multiple independent windows
> for the various runs and you don't mind that the runs will interfere
> with each other (that is, that only one of them can actually do
> calculations at any one time, with the others being shut out of
> continuing until the routine does the calculation allows interrupts by
> doing a pause() or drawnow() or the like.)

Thank you sooo much =) It exactly what i'm looking for.. ;)
 | 
Pages: 1
Prev: fprintf problems
Next: serial communication