What are the benefits of using MUI 4.0 for development vs 3.9? We are developing Aladdin 4D 6.0 and use MUI for our GUI toolkit. A4D is for both Amiga OS 4.1 & MorphOS 2.x. We can't use MUI 4 on both OSes since only MorphOS has the latest version.

Is MUI4.0 MorphOS native and 3.9 is 680x0? Just a quick guess without doing any research on my own.

MUI 3.9 is PPC on Amiga OS 4.1.

The main benefit would be the time that has to be spent on the project - with MUI 4 many things that take hours with 3.9 are down to just a DoMethod call - for instance: dynamic tabs can be done with MUI3.9 but require a lot of manual hacking while they're automagic with MUI4.

dynamic tabs can be done with MUI3.9 but require a lot of manual hacking while they're automagic with MUI4.

Who came up with this weird implementation/design of dynamic tabs? Stuntzi himself? In OWB sources I saw a triply nested MUIM_Group_InitChange/MUIM_Group_ExitChange while adding new tab ...

Quote:

He has indeed. Mind that it's unfinished and the API isn't really public (not part of official SDK).

So back to topic: What are the benefits of Mui 4 besides dynamic tabs (I even donnot know what dynamic
tabs are, are there static tabs)?

What is a dynamic tab? A tab that disappears under some condition? Or of variable size? DEpending on what?

Quote:

There are MUI 4 versions for 68k and OS4 now.
http://muidev.de/downloads/

However, differences aren`t well documented or I can`t find much. It seems a lot are visual advancements too

Hope this show of some MUI4 advancements helps
http://library.morph.zone/Magic_User_Interface_Programming

Quote:

In MUI3, the tabs could only be set at group initialization and one had to re-create the group object to change them (doable, but cumbersome, MUICON did that for example).

MUI4 is much easier to use when creating interfaces dynamically. It makes it easier to write multithreaded applications as well as adds a lot of new classes.

Quote:
While both 3.9 and 4.0 are based on the same sources, 3.9 is based on much older version, which means 2 things:
1)It's generally lacking features that 4.0 has
2)It's trying to replicate newer functionality, sometimes with more, sometimes with less success.

So 4.0 is "more complete" in general.

Also, should probably define what "MUI3.9 development" means. It can mean developing for 68k or OS4 (as those are the platforms it's available for, not sure about AROS) or it can mean "general" MUI development for common & properly working functionality available in both, then compiling for "best MUI available" for the current platform (and hope it works). Second is of course a much better choice.

> not sure about AROS

MUI 3.9 (and MUI 4.0) for m68k should run on AROS/m68k.

so a dynamic tab is a tab that is added or removed after the program has completely started? like a tab in Odyssey? I remember IBrowse could do this, too.