or Connect
New Posts  All Forums:

Posts by Mr Beardsley

I believe it was Tranquility.
Actually it is 4 times. 200 ppi vs 100 ppi is 4 times the number of pixels. Take a 1"x1" image for example. At 100 ppi that's 100 x 100 = 10,000 pixels. At 200 ppi that's 200 x 200 = 40,000 pixels. At 300 ppi that's 300 x 300 = 90,000 pixels. Basic math .
NSTextField inherits from NSControl which has the following methods: – doubleValue – setDoubleValue: – floatValue – setFloatValue: – intValue – setIntValue: – objectValue – setObjectValue: – stringValue – setStringValue: – attributedStringValue – setAttributedStringValue:
After reading that paper, my position is not changed at all. It would seem they worked very hard at making sure the outcome supported their hypothesis. They didn't use a better allocator which goes hand in hand with GC, they restricted testing multi-threaded GC. In fact the paper showed that under certain circumstances the GenMS garbage collector can be faster then manual memory management. The downside is that GenMS doesn't play well with small heap sizes. Their is...
First, you really know what I do for a living? Interesting that you can know that about me. I guess writing C++ MFC applications for a government contractor means I'm not a developer. Man, you should really tell the company that I work for that I don't really do what they think I do. Second, is cleaning up files and database connections the general case of deallocating most objects? That is more of a special case that can easily be handled even while using GC. My...
Maybe you should read up a little on modern GC. Why would you need to send an object the dealloc message? The only reason those are useful today is to clean up after yourself when freeing up an object. There will be no reason to put anything in the dealloc method once the GC is taking care of it.http://www.iecc.com/gclist/GC-faq.html
What's interesting is that in almost all cases* GC will be faster than Cocoa's retain/release method. I agree that retain/release is about as good as it gets regarding manual memory management, but there is a lot of messaging overhead with that method. When the AutoReleasePool is released, it in turn sends a release message to all the objects it contains. This can add up to a lot of messages depending on the situation. Now with something like a mark and sweep...
I know real developers use assembly because using higher levels of abstraction that make you more productive as a dev just isn't the mac way.
The KPs sound like bad hardware. My first bet would be bad RAM. If you have more than one stick of RAM in the machine try running on 1 at a time to see if you can isolate which stick is causing the problem.
Try doing a "Get Info" on the secondary drive, and select "Ignore Permission on this Drive".
New Posts  All Forums: