[FIXED] MUI4 Textinputscroll.mcc

[chris]

I have an old program I still use which needs textinputscroll.mcc. The update to MUI4 included a new version of this class, however I think there is something wrong with the version numbering as I get the following error:


You will note that the similar textinput.mcc (which was also updated with MUI4) is reporting the version correctly, however textinputscroll.mcc is not.

The version command is reporting the correct strings:

Code: Select all

8.AmigaOS:> version textinputscroll.mcc full
Textinputscroll.mcc 30.0 (16/10/2011)
Copyright (C) 1997-2003 Oliver Wagner, Copyright (C) 2006-2013 Thore Boeckelmann, Jens Maus [AmigaOS4/PPC] [svn r2948]
8.AmigaOS:> version mui:libs/mui/textinputscroll.old.mcc full
Textinputscroll.mcc 29.5 (22/12/2001)
© 1997-2001 Oliver Wagner <[email protected]>, All Rights Reserved

So I think it is probably just the numeric VERSION which is wrong.

If I replace with the old version it continues to work correctly. Also note that the revision number of 0 which has been used is technically invalid (and leads me to believe bumprev has not been used for these components).

[tboeckel]

If I replace with the old version it continues to work correctly. Also note that the revision number of 0 which has been used is technically invalid (and leads me to believe bumprev has not been used for these components).

MUI classes have two versions (which of course should be identical):
1. the version included in the typical $VER: version string
2. the version+revision returned by MUIA_Version/Revision

The first is obtained by C:Version for example. That's why you get a correct version output in the shell. However, the latter was missing for both classes. The fact that Textinput.mcc nevertheless returned "30.0" as version is due to the fact that it is a subclass of String.mui which in turn does implement get()ing these two attributes. That is why Textinput.mcc returns a correct version/revision and Textinputscroll.mcc as a subclass of Group.mui does not.

This issue is already fixed. Just wait for the next release.

[chris]

Excellent, thanks.

[chris]

Hmm, if that was in the update I spotted today, then it hasn't fixed it.

[tboeckel]

Hmm, if that was in the update I spotted today, then it hasn't fixed it.

Unfortunately the last release has been published before this issues was fixed. Take a look at the date. It is dated December 22nd 2013.

[chris]

Hmm, if that was in the update I spotted today, then it hasn't fixed it.

Unfortunately the last release has been published before this issues was fixed. Take a look at the date. It is dated December 22nd 2013.

Pleased to report this is fixed with the latest update. Thanks!