Menu
▾
▴
#449 Creating cycle object without MUIA_Cycle_Entries fails
In contrast to MUI it is not possible to create an instance of Cycle.mui without an initial MUIA_Cycle_Entries attribute. MUI silently falls back to an entry array like { "", NULL } and never fails.
This was the reason why YAM 2.8 was not able to open its configuration window, because the entries of certain cycle objects are populated right after creating the object.
My copy of the MUI docs state that the cycle entries list can only be populated during initialisation.
This is true. But in fact setting MUIA_Cycle_Entries already works with MUI 3.8 and since MUI 3.9 this attribute is officially settable.
This should be fixed with r47564 (ABIv1) and r47566 (ABIv0), and in the next nightly builds.
BTW, sorry Thore, I didn't see your reply to my question until a few days ago as I was expecting notification from SF, which never came. Do you know if this attribute is also gettable now?
No, MUIA_Cycle_Entries is still [is.]. Since you have to make sure that all the entry string stay valid as long as the cycle object knows them there is no point in being able to OM_GET them.