🚀 go-pugleaf

Hello Amiganoids|

=======WARNING: a (little bit)larger file follows: ==================

This discussion about mutualexclude Gadgets starts to be boring
(at least to me ;-) |

Facts are:
-The MutEx doesn't work at all (still Kick1.3).
-The description in the Include's are wrong (well, at least not complete
 correctly).
-The mutualexclude-field in the Gadget-structure is a 32Bit-wide ULONG.

Well, now the problems:
-32 bits ARE NOT enough to use them as a bit-field (like the mutexcld-
 field in the MenuItem-structure, 32 Menus including 32 MenuItems incl.
 32 SubItems ARE enough (for me ;-)); 32 Gadget's AREN'T |||

It's nice C= had felt even so; let them use this field as a pointer|
but a pointer to what ? a extended structure(like a quadword(64Bit)?)
a pointer to a system-function ?  a pointer to a user-defined-function ?
C= HAD TO explain ALL Amiga-programmers (not just subscribed developers),
HOW to use them, if they are implemented, or  HAD TO mark them as unused,
if they are not (like at the moment).
C= has passed it - that's ugly , but why still flaming about it ?

This mistake of C= (neither implementing, nor marking the MuEx) IS
NOT a reason to self-implement the mutual-exclusion in THIS way |
I don't say all system-fields are untouchable ( nice example: the
NextGadget-field :-) ), but there is a great difference between
KNOWING the meaning of a field, and GUESSING it |
You KNOW the meaning of the NextGadget-field (it is really a
32Bit-significant ( don't forget 32, not just 24 |||) Memory-pointer,
nothing else |), but all you know about the Mutual-Exclude--field is:
it is a 32Bit-wide (ULONG) space in the struct|
You've guessed the meaning of this field ( 32Bit-bit-field => 32
mutual-excludable Gadgets ). Well, C= had written it in the includes,
you're right, but you must accept the following :
You have to GUESS the meaning of any field at any structure, since
it is not implemented.
This is the fact not just at the mutualexclude-field, but also at ALL
unimplemented fields in the system. You have to accept this, or
stop programming (compatible) software (this isn't a flame, just the
truth ;-) ).
And if you must guess the meaning, you mustn't use it |

If all programmers stop guessing things like this, much more software
would be compatible with things, the future brings to us.
C= had ever telled (at least since 1987 |||),that they plan to add (at
least) one address-pin to the custom-chips, resulting more CHIP-RAM.
Much (too much) software is still confused finding 1MByte |||).
I hope programmers will learn, that they aren't alone; a bit more
discipline in programming would be very, very nice.
How to self-implement such problems like mutual-exclude is discussed
further in this list, I will now stop bubbling ;-) |
I wish you all a happy new year,
                           Walter Mildenberger <Kurs12@DHVMHH1>.Bitnet
p.S: I know I say a lot of times "at least" :-)
p.p.S: I'm now a little bit confused: there aren't 32 Menus and 32 MenuItems
      and 32 SubItems etc. but how much really ?|?