It's surely a noob question: in every skeleton-code i found there's no way to find a "main loop".
i simply look at a series of "domethod", one after another, to notify between objects or at the best a switch-case where the code switches different ids (#define myroutine 55) to "play" code.
Is the "main loop" hidden somewhere?
what numbers can i use to define ids? are there some reserved ids?

Because MUI no more uses main loop to handle events.

The correct way is now subclassing and adding methods. See example classX.c in MUI examples in SDK. This is a good starting point.

++

It's just like Tcheko said: main loops are a thing of the past when oo programming waasn't very popular on Amiga. It's the same with hooks. So, in order to handle notifications from buttons and so on you subclass Application.mui, Window.mui or some Group.mui of your choice, define your own private methods there and setup notifications on your buttons to call these methods. This lets you keep a neat internal structure rather than having everything in a one huge switch statement.

To define your own private method and attribute ids you could start with TAG_USER.

Well actually there is small main-loop at the end of every example waiting just for the user to quit, either by closeing the window or hitting CTRL-C.

Envbrowser.c even has an oldstyle main-loop with input-IDs for every gadget.

But as allready pointed out notification and subclassing can be very powerfull and leads to better code ..... well atleast if done right ;)

A MUI program has a main loop, just in the ideal application the loop is empty. I recommend this article, I guess it gives some explanation .