FROM : JongAm Park
DATE : Tue Jul 01 23:15:39 2008
Hello, all.
I solved this problem for myself.
The reason was that the Tiger behaves differently from the Leopard.
On a Tiger ( MacPro 2 2.66Ghz DualCore Intel Xeon processor ), it needed
a call setScalesWhenResized: .
So the whole code looks like :
NSSize imageSize;
activeCompanyImage = [[NSImage alloc]
initWithContentsOfFile:activeCompanyImagePath];
imageSize = [activeCompanyImage size];
imageSize.width *= 0.3;
imageSize.height *= 0.3;
[activeCompanyImage *setScalesWhenResized*:YES]; // This line is
additional for the Tiger
[activeCompanyImage setSize:imageSize];
I would like to report this.
Should it be a bug? Or just some note on the documentation can be enough?
DATE : Tue Jul 01 23:15:39 2008
Hello, all.
I solved this problem for myself.
The reason was that the Tiger behaves differently from the Leopard.
On a Tiger ( MacPro 2 2.66Ghz DualCore Intel Xeon processor ), it needed
a call setScalesWhenResized: .
So the whole code looks like :
NSSize imageSize;
activeCompanyImage = [[NSImage alloc]
initWithContentsOfFile:activeCompanyImagePath];
imageSize = [activeCompanyImage size];
imageSize.width *= 0.3;
imageSize.height *= 0.3;
[activeCompanyImage *setScalesWhenResized*:YES]; // This line is
additional for the Tiger
[activeCompanyImage setSize:imageSize];
I would like to report this.
Should it be a bug? Or just some note on the documentation can be enough?
| Related mails | Author | Date |
|---|---|---|
| JongAm Park | Jul 1, 16:53 | |
| Peter Ammon | Jul 1, 20:34 | |
| Nathan Kinsinger | Jul 1, 21:34 | |
| JongAm Park | Jul 1, 22:29 | |
| JongAm Park | Jul 1, 22:34 | |
| JongAm Park | Jul 1, 23:15 | |
| JongAm Park | Jul 1, 23:15 |






Cocoa mail archive

