Default constructor

For MUI's automatic layout system, it's required that objects know their minimum and maximums sizes. Since boopsi gadgets don't support this feature, you will have to help MUI and adjust these values by hand.

Defaults:

MUIA_Boopsi_MinWidth - 1 pixel MUIA_Boopsi_MinHeight - 1 pixel MUIA_Boopsi_MaxWidth - unlimited MUIA_Boopsi_MaxHeight - unlimited

For MUI's automatic layout system, it's required that objects know their minimum and maximums sizes. Since boopsi gadgets don't support this feature, you will have to help MUI and adjust these values by hand.

Defaults:

MUIA_Boopsi_MinWidth - 1 pixel MUIA_Boopsi_MinHeight - 1 pixel MUIA_Boopsi_MaxWidth - unlimited MUIA_Boopsi_MaxHeight - unlimited

MUIA_Boopsi_ClassID specifies the name for the public Boopsi class you want to create an object of. It will only be used when MUIA_Boopsi_Class is NULL.

The public class must be in memory before you can create an instance of it, you will have to open the required class library by hand.

Note the string given to MUIA_Boopsi_ClassID must remain valid until you're done with the object.

Pointer to the (private) class you want to create a boopsi object from. Only useful if you previously generated your own boopsi class with MakeClass().

Of course you may not free the class until you're done with your object.

For MUI's automatic layout system, it's required that objects know their minimum and maximums sizes. Since boopsi gadgets don't support this feature, you will have to help MUI and adjust these values by hand.

Defaults:

MUIA_Boopsi_MinWidth - 1 pixel MUIA_Boopsi_MinHeight - 1 pixel MUIA_Boopsi_MaxWidth - unlimited MUIA_Boopsi_MaxHeight - unlimited

For MUI's automatic layout system, it's required that objects know their minimum and maximums sizes. Since boopsi gadgets don't support this feature, you will have to help MUI and adjust these values by hand.

Defaults:

MUIA_Boopsi_MinWidth - 1 pixel MUIA_Boopsi_MinHeight - 1 pixel MUIA_Boopsi_MaxWidth - unlimited MUIA_Boopsi_MaxHeight - unlimited

No input, just an output since this attribute is only getable. What MUI returns when generating a BoopsiObject is a standard MUI object, not a pointer to the Boopsi gadget itself. In case you really need this Boopsi gadget pointer, you can obtain it by getting MUIA_Boopsi_Object from the MUI object.

Since MUI passes along every unknown attribute to the boopsi gadget, there should be no need for this tag anyway.

Note that the boopsi object pointer is only valid when the window is open!

CAUTION: this is an initializer attribute, meaning it cannot be changed after the underlying MUI object is instantiated

CAUTION: this is an initializer attribute, meaning it cannot be changed after the underlying MUI object is instantiated

Unfortunately, most boopsi gadgets need information on the display environment they will reside in at object creation time. Due to MUI's concept, this information is not available that early.

To solve this problem, MUI doesn't generate the boopsi object instantly, creation is delayed until the window containing the gadget is opened.

At this time, MUI fills some values about display environment into the boopsi objects creation tag list. You have to tell MUI, what tags are actually needed.

With MUIA_Boopsi_TagDrawInfo you can tell MUI where to fill in a needed DrawInfo structure.

Unfortunately, most boopsi gadgets need information on the display environment they will reside in at object creation time. Due to MUI's concept, this information is not available that early.

To solve this problem, MUI doesn't generate the boopsi object instantly, creation is delayed until the window containing the gadget is opened.

At this time, MUI fills some values about display environment into the boopsi objects creation tag list. You have to tell MUI, what tags are actually needed.

With MUIA_Boopsi_TagScreen you can tell MUI where to fill in a needed Screen structure.

Unfortunately, most boopsi gadgets need information on the display environment they will reside in at object creation time. Due to MUI's concept, this information is not available that early.

To solve this problem, MUI doesn't generate the boopsi object instantly, creation is delayed until the window containing the gadget is opened.

At this time, MUI fills some values about display environment into the boopsi objects creation tag list. You have to tell MUI, what tags are actually needed.

With MUIA_Boopsi_TagWindow you can tell MUI where to fill in a needed Window structure.