I think that the best news about this new portal is the possibility to post and talk directly with developers about specific bug reports, so let's go
During our port (AmiArcadia, Saga, Koules and so on) from OS3 to OS4 me and James Jacobs have found some various bugs & incompatibilities in OS4 that maybe are not reported on the official bug tracker yet (or already fixed in Update 3), so here the list:
------------------------------------------
OS4.1 Bugs
----------
Only bugs which are still present under OS4.1.1 are listed. These bugs do
not occur under OS3.9.
The OS3.9 bugs which are listed above may or may not be present under
OS4.1.1.
exec.library:
(*) Alert() is broken: Alerts cannot be closed on a SAM; only on a
PS/2 interface, not a USB or Synergyc interface. Consequently,
DisplayAlert() (in intution.library) is likewise broken. (You can
use http://aminet.net/util/misc/AlPatch.lha (or similar) to work
around this.)
Installer:
(*) Installer V44 functionality (such as the "effect" command) is not
supported by the OS4.x Installer and will cause the script to abort
with an error message.
intuition.library:
(a) MENUDISABLEDTEXTPEN does not exist. Therefore, there is no method of
specifying the colour for the text of disabled menus and menu items.
Using the SA_LikeWorkbench, TRUE tag seems to help AmigaOS to choose a
reasonable pen for this.
(b) It isn't documented which pen is used for the highlight on selected
menu items. It is probably SELECTPEN, but could possibly instead be
GLYPHFILLPEN or FILLFLATPEN. (Not strictly a bug.)
(c) To get sticky menu support, you need to use the SA_LikeWorkbench, TRUE
tag.
keyboard.device:
(*) KBD_READMATRIX does not work correctly (returns 0s for all keys).
ReAction:
(*) When you click on any button with mixed text and graphics, they don't
have a transparence effect. It shows a coloured background around the
text when pressed. You need to use the BITMAP_Transparent tag (and perhaps
BITMAP_Masking?).
Version:
(a) Version strings which are not prepended by a NUL ($00) byte are not
parsed correctly.
(b) Multiple version strings in one file confuse the parser.
(c) "If I create a file with nothing but the OS3 executable identifier
($000003F3) at the beginning followed by a valid version string, the
Version command won't find the version. If the executable identifier
is replaced with anything else (binary or alphanumeric) then the
Version command works. My suspicion is that if the Version command
finds an OS3 executable identifier at the beginning of a file, it only
looks for a version string in a particular type of Amiga OS hunk. If
that's not the case then it is a complete mystery to me. Regardless,
the Version command should get fixed for the next OS4 release."
------------------------------------------------------------
GCC 4.2.4 Bugs
------------------------------------------------------------
The optimizer has bugs. Eg. when using -O1 or -O2 to compile Koules 1.16
for OS4, the resulting executable has a bug: namely, that the P key only
pauses while it is held down. Compiling with -O0 avoids this issue.
More info at: http://amigan.1emu.net/releases/ami-code.txt
