@Valiant

Quote:

Quote:

Ouch! That definitively shouldn't happen, be AISS installed or not. Feel free to send me a log of the crash at the address mentioned in the archive (after a complete lock up, you can still generate a report typing "dumpdebugbuffer ram>log.txt clear" in a shell after a "soft" reset).

@Amigo1

IMHO, Feelin is very promising and offers new interesting features, the problem is that the API is still changing (faster than the builtin classes...) and the developer archive contains a significative amount of things "under construction".
It has several advantages over MUI/ReAction (no BOOPSI, XML stuff, ...) but ATM I'm not sure you have the minimum required for the typical GUI (e.g. : no menus).
Otherwise, it would be also a good candidate

@DiscreetFX

I'll second for MUI, though I currently use ReAction for programming. If you plan to build versions for other systems this is the best choice, and besides that it has more high level features and classes than ReAction.
Current OS4 version of MUI is way outdated and a bit buggy (vertical gradients, etc...), but I'm still hoping for a MUI4 port that would change the deal

@Hans

I mean DOS process, the parent/child feature is available through DOS function CreateNewProcTags().

@Hans

AFAIK, at the moment you'd better use MEMF_SHARED memory between your different processes because parent process memory flagged as MEMF_PRIVATE is not shared with its children (NP_Child flag) (someone correct me if I'm wrong).