RadarWeb Bug Report

adam.roth wrote:
Additionally I would like to lodge a formal complaint against RadarWeb:

*Problem Description*
RadarWeb is one of the worst bug reporting tools I have ever used. It has too many fields in too many sections (am I seriously expected to specify a schedule for each bug I submit? How am I supposed to know what sort of schedule is reasonable? How about showing me your current development calendar if you want to me provide a schedule for fixing the bug?). It screws up and loses my bug reports. I hit 'Save' but it doesn't save anything. It tells me "No matching components found" but doesn't give me any indications as to what a valid combination of Component+Version would be. The "Find Component" tool never finds any components. It forgets everything I've done after two hours (what is this, the 1990's?) instead of auto-saving my work and caching it with my user account. I have legitimate bugs to submit, but this useless tool is not letting me.

I propose you replace RadarWeb with an issue tracking system that actually works, like JIRA.

Workaround
Don't bother being responsible about reporting bugs that you find...

adam.roth wrote:
Source-code that reproduces the issue is here: UITableViewTest.zip

adam.roth wrote:
*Problem Description*
UITableViewCell.imageView incorrectly scales its image attribute, even when the developer has programmatically applied a different scale factor to the image being used. This only happens if the image is scaled using UIImageOrientationUp. If any other orientation is used, then the programmatic scale factor is respected.

 cell.imageView.image = [UIImage imageNamed:IMAGE_NAME];
 
 CGAffineTransform transform = CGAffineTransformMakeScale(.5, .5);
 cell.imageView.transform = transform;

adam.roth wrote:
Nope, didn't do any of that. All I did was 'New Project...' (using the "View-based Application" template) in XCode4. I specified a folder for the project, and everything else is as the IDE created it. I confirmed this by creating a new test project. It got the exact same layout by default. XCode4 just does things differently ("it's too advanced to be compatible with anything else!").

I guess I should have noted on the download that the project should be opened with XCode4.

adam.roth wrote:
That's a nice workaround, certainly better than storing an inverted copy of the image. Still doesn't explain why the rendering is different between the first cell and all the subsequent cells though. At a minimum I'd expect the behavior to be consistent. And I did notice the error messages, but I found some posts on stackoverflow or some similar site that made it sound like a known issue of some sort. The rotation and scale appeared to always be applied correctly (except for the first cell), so I didn't worry too much about the error log.

Yep, at least that's what it does if you do 'New File...' and then select "UIViewController subclass".

No, it won't let me look at them. I get a nice red error message along the lines of "No items were found that match the search criteria (The search may have failed if you do not have enough privileges to view the search result)". But I think you're probably right, although I have no idea how/why I would have been given internal access to RadarWeb.

adam.roth wrote:
The non-internal version is much more usable, though I kind of feel sorry for Apple employees if they're stuck using the version that I was seeing.

Did you ever get an answer to this, I too see this very complex form that does nothing but say "No matching components found". I'm trying to report some serious UI/Usability issues in Mountain Lion components.