Thank you, Simon and Rex, for your replies. I was afraid that would be the answer I received. This type of conclusion is all too common among these forums. I've been developing for the BlackBerry platform for less than a year, and I've been utterly dumbfounded by the half-baked and frustratingly limited API put-out by RIM. Using the ApplicationMenuItem class is one of the only means by which we can hook-into their built-in apps and achieve some sense of fluidity. For it to be so inconsistent, and for the most part, broken in most of their OS versions, is just inexcusable. I sure hope this type of API negligance is improving. I can't imagine it being much worse.
Rex, since you have products which rely on this broken feature, how do you deal with it? Telling the end-user that it's a bug in RIM's API is certainly not going to make them any less frustrated toward your product. How do you code around something like this when there's no other way to access the information that, according to their documentation, is supposed to be passed to your run method?
