MUIV_Application_ReturnID_Quit question

5 posts / 0 new

Last post

Sun, 2014-02-16 12:45

trixie

Offline

Last seen: 6 months 3 weeks ago

Joined: 2011-02-03 13:58

MUIV_Application_ReturnID_Quit question

I have a question concerning MUIV_Application_ReturnID_Quit in MUI. The autodoc says that "the ideal input loop for an object oriented MUI application" should look like this:

	{
	   ULONG sigs = 0;
 
	   while (DoMethod(app,MUIM_Application_NewInput,&sigs)
	          !=MUIV_Application_ReturnID_Quit)
	   {
	      if (sigs)
	      {
	         sigs = Wait(sigs | SIGBREAKF_CTRL_C);
	         if (sigs & SIGBREAKF_CTRL_C) break;
	      }
	   }
	}

The input loop ends when the MUIM_Application_NewInput method says that the program shall terminate (e.g. upon receiving a window close event). Having no previous experience with MUI, I'd like to know how quit confirmation (such as displaying an "Are you sure?" requester) is best handled, after MUIV_Application_ReturnID_Quit breaks the input loop.

Mon, 2014-02-17 00:27

thomas

Offline

Last seen: 3 months 1 week ago

Joined: 2011-05-16 14:23

This should look familiar to

This should look familiar to a ReAction coder:

BOOL done = FALSE;
ULONG mui_sigs = 0;
ULONG other_sigs = whatever;
 
while (!done)
{
	ULONG sigs_recvd = 0;
 
	if (mui_sigs)
		sigs_recvd = Wait (mui_sigs | other_sigs | SIGBREAKF_CTRL_C);
 
	if (sigs_recvd & SIGBREAKF_CTRL_C)
	{
		Printf ("*** Break\n");
		done = TRUE;
	}
 
	if (sigs_recvd & other_sigs)
	{
		handle_other_things();
	}
 
	switch (DoMethod (app,MUIM_Application_NewInput,&sigs))
	{
	case ideally_here_should_be_nothing_but_you_never_know:
		handle_this();
		break;
	case MUIV_Application_ReturnID_Quit:
		if (are_you_sure())
			done = TRUE;
		break;
	}
}

Note: I've written this from memory. I'll look up real existing (and working) MUI code of mine tomorrow.

Mon, 2014-02-17 00:29

(Reply to #2) #3

trixie

Offline

Last seen: 6 months 3 weeks ago

Joined: 2011-02-03 13:58

Re: MUIV_Application_ReturnID_Quit question

I'll look up real existing (and working) MUI code of mine tomorrow.

Thank you Thomas, really appreciated!

AmigaOne X5000-020 / 2GB RAM / Sapphire Pulse Radeon RX 560 / AmigaOS 4.1 Final Edition Update 2

Mon, 2014-02-17 07:27

(Reply to #3) #4

kas1e

Offline

Last seen: 3 months 1 week ago

Joined: 2010-11-30 15:30

@Trixie Not related to what

@Trixie
Not related to what you ask exactly, but still about "ideal mui loop": year ago i ask Thore to implement MUIM_Application_Execute() to make AROS code be more easy portable (that function come from AROS's ZUNE), and so he add it, and in changelog it stated as "* Application.c: added the method MUIM_Application_Execute which implements the ideal main loop for an MUI application". The code of that MUIM_Application_Execute (at least on AROS), are:

IPTR Application_Execute(Class *CLASS, Object *self, Msg message)
{
     ULONG signals = 0L;
     
     while
     ( 
            DoMethod(self, MUIM_Application_NewInput, (IPTR) &signals) 
         != MUIV_Application_ReturnID_Quit
     )
     {
         if (signals)
         {
             signals = Wait(signals | SIGBREAKF_CTRL_C);
             if (signals & SIGBREAKF_CTRL_C) break;
         }
     }
     
     return NULL;
}

And so you can just use now in our mui that MUIM_Application_Execute() directly, something like:

main()
{ 
   ..balbala..
 
   SET(win, MUIA_Window_Open, TRUE);
   DoMethod(app, MUIM_Application_Execute);
 
   ... blablabla.... 
}

Mon, 2014-02-17 13:01

(Reply to #4) #5

salass00

Offline

Last seen: 6 months 2 weeks ago

Joined: 2011-02-03 11:27

Combining thomas' and kas1e's

Combining thomas' and kas1e's code you could do:

BOOL done = FALSE;
do {
    DoMethod(app, MUIM_Application_Execute);
} while (!are_you_sure());

Search form

User login