On 09/05/2012, at 7:45 PM, ecir hana wrote: > I'm sorry for such basic questions I'm very new to all this.
We did warn you that taking yourself down this path wasn't going to be the best idea. Now you're seeing why. If you build a document-based app using Xcode's template, it will work correctly from the very first time you run it. Then you can see how it's put together, and all of these things will slowly become obvious. Analogy: if you take apart a clock, you might not understand at first how it works, but you have the correct pieces which, when put together properly, would make a working clock. By studying these pieces, you could work out how it works. What you are doing is starting with sheets of brass and miscellaneous screws and trying to make a working clock without having any knowledge of how a clock should work, or how it is typically made, beyond perhaps some idea about how gears work. At the very least if you insist on this approach, you should read all of the documentation thoroughly, so you understand the (many) concepts that lie behind Cocoa's architecture. The behaviour of an application is not down to just one object's behaviour, but the intricate interaction between many different objects. Stumbling across the correct connections to all of those objects more or less by chance is very improbable. But starting with an app already correctly working and connected will give you something to study. --Graham _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
