MorphOS Developer
Posts: 2997 from 2003/3/5
From: Canada
Quote:
Georg wrote:
Some things are not documented at all (TAG_IGNORE, special treatment/filtering/... of attributes/methods in certain classes, ...). Some things are documented wrongly (attributes which know OM_GET).
That's called the "know how" ;) From a MUI application programmer's POV you really don't need to know how those internals work, do you?
Quote:
Georg wrote:
There are also some buggy things in MUI itself. Like MUIA_ShowMe. To be compatible you are not even allowed to make a non-buggy version of this. You would need to reproduce the exact same buggy behaviour to be really compatible. Great ...
MUIA_ShowMe was actually fixed in MUI4. Still, a lot of internal hickups do come from the fact that certain applications; namely Vaporware (does anyone remember Voyager?) and, even worse, IBrowse do rely on many MUI internals. That's not just internal methods/attrs, but the layout of object data structures. Trying to get those legacy (cr)apps to continue working with a modern MUI was a challenge and the result is that some stuff may be hard for you to understand just by testing/reading docs. Especially since MUI does have a lot of code that actually works around bugs in applications (IBrowse ;) ...
