If not (or if an additional report will make a difference), I will
report it in radar.
There's no need to worry about whether a problem is known or not.
Just file the bug report, including everything needed for us to
reproduce the problem. A large number of related reports can tell us
how widespread a problem is.
I can see why at your end there is no reason to worry whether a bug
is know or not. For me, as a developer it does make a huge difference
for several reasons:
1) It could be that I am wrong and that it is no bug but an error on
my end or a "feature" that behaves as expected (no need to write it
up in these cases).
2) If it is a know bug a workaround may also be available. if I just
file the bug it can take weeks if not months before someone tells me
it is a known bug and that there is an easy work around.
3) If it is a known bug it could be that it is already fixed for a
future release. No need for me to write up a bug report in that case.
4) If it is not just a know but a well known bug chances are that
adding yet another report is not going to make much of a difference.
5) If it is an unknown bug or one not going to be prioritized
(because Apple deems it low priority) unless many people write in bug
reports on it then it is worthwhile writing up a report.
6) Writing up a report for a known bug may be useful to prioritize it
but it is very ungratifying for a developer to write up such a bug
because it will be marked as a duplicate and the developer will not
be kept informed if and when the bug will be fixed nor can he see
anything in radar but the fact that it is a duplicate. The only way
to find out about the progress on a duplicate is to write into
devbugs and ask. that is not something anyone would want to do weekly
or so as it waistes everyones time and bandwidth.
7) Writing up a good bug report "including everything needed for us
to reproduce the problem", as you state it, takes quite a bit of time
and may even involve making a sample project to demonstrate the
issue. Writing up a good bug report can take anywhere from 15-30
minutes to a couple of hours depending on the issue. I would happily
invest that time if I know it will make a difference, but not if it
is not neccesary for one of the reasons mentioned above. Or, in case
it is a known issue that can use some more priotarization, I would
write up a minimal report in 5-10 minutes without all the detailed
documentation needed to isolate a new issue.
Anyway, to make a long story short I have just reported the bug as
Bug ID 3524888.
Is it possible that you somehow got the cookies reversed for the two keys?
I don't think so. I lookup the relation between cookies and usage
values on the fly after the user selects a particular keyboard to
work with. Also, the problem does not occur with an external keyboard
only with the build in Powerbook keyboard.
Instructions to reproduce the problem are in my bug report (Bug ID 3524888).
At this point for me the most important thing to know is whether this
is likely to be a problem only with the built-in keyboards of the
powerbooks, or also with the iBooks or even with all ADB keyboards. I
don't have the machines available to test this but it would be
worthwhil knowing this in order to create a temporary workaround.
Thanks,
david.
_______________________________________________
usb mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/usb
Do not post admin requests to the list. They will be ignored.
