Basically, there are three possible solutions:

2. Bind to a different object in the nib rather than to the File’s Owner.

Sounds like the reason I’ve been looking for to use NSObjectController.

———
Tony

Cognitive AB, Stelvio Bokföring Lön Ekonomi för Macintosh
http://www.ct.se/

Thanx, just what I needed for my new Mac apps

Tony

Cognitive AB, Stelvio Bokföring Lön Ekonomi för Macintosh
http://www.ct.se/

[1] http://cr.yp.to/proto/netstrings.txt

I thought I had my RSS feeds under control, but now I’ve got an additional 2000-off Cocoa Dev articles in the queue..

Grrrr!

I can write to that file, so why I can’t I change what’s in it? Grrr… stupid mycompany.com and their stupid LapCatDocCtrl application.

That’s a very good point. The app developers will get blamed, and then we’ll be forced to try to explain Leopard’s weirdness to the user.

I agree with you though that this isn’t a security problem (as Cocoa is being less permissive than the filesystem would allow), it certainly could catch users out though.

After that, you can use “syslog -k Facility com.apple.console -k Level gt 3″ to see the messages that were filtered out.

PS: In Mail.app, that’s localized ressources that take place (about 15MB per language), so removing unused languages will do the trick.

And I have been looking for a good replacement for OO anyway, for a number of reasons. (A *binary* file format? For an outliner!? etc)

Poor Omni. I should send flowers

The contractor isn’t necessarily a fool, however this was dumb, that much is clear. However i believe the author should have commented this. Especially if it caused a build warning, but was actually correctly implemented.

[blockquote]
What is this written in? I think C# has a preprocessor directive to supress compiler warnings like that if you want to.
[/blockquote]

GCC has that too. But we, ObjC programmers, turn on ALL compiler warnings (part of that is due to the dynamic nature of ObjC).

Brian pointed out the correct way to avoid this warning.

P.S. One warning I hate is when you don’t add a new line after if () without braces – gcc tells us that we possibly missed the braces.

The correct way to do it is:

while((aDict = [fileEnum nextObject]) != NULL)

(or whatever ‘null’ passes for in that language).

The programmer should not indulge in clever terseness at the expense of clarity and maintainability.

One thing I’d recommend is commenting assignments inside if/while etc. Even something as trivial as “// Yes, = is intended” should be sufficient. I’ve had something similar happen to me once (someone added a break to a switch-case I’d written correctly without a break, they thought it was left out by mistake). Dont underestimate the adage “a little knowledge is a dangerous thing”.

The similarity between = and == ? How about the similarity between Duck and Suck? We’ve got a loose canon there guys. Watch out or pretty soon we’ll have childrens’ shows where the presenters utter obscenities by accident.

Not using assignment in while? Oh, lord forbid using a clearly defined feature in the language.

For those who have problems with these operations: wake up and read the reference just once. If the reference is too much for you, just read a tutorial which will mention these in the opening chapters. Not every language is Visual Basic.

while((aDict = [fileEnum nextObject]))

The warning emitted by gcc is something along the lines of “suggest double parentheses around assignment used in truth value”.

Of course, whether adding an extra set of parentheses to disambiguate this case is enough or the correct solution is open to debate. But changing the semantics of the program certainly isn’t correct.

Not really. You still have the same problem with int if the result of the bitwise operation is larger than an int. Using the result of a bitwise operation as a Boolean value is risky and needlessly terse at best. Take the extra time to write what you really mean, as the author suggests.

A bitwise operator, in contrast, can return any bit field.

I believe you meant bit mask here. A bit field is a specific pattern of structure members, like this:

unsigned reserved: 5;
unsigned hallLightSwitches: 2;
unsigned masterBedroomLightSwitch: 1;
unsigned childBedroomLightSwitch: 1;
unsigned guestBedroomLightSwitch: 1;
unsigned bathroomLightSwitch0: 1;
unsigned bathroomLightSwitch1: 1;
unsigned livingRoomLightSwitch: 1;
unsigned diningRoomLightSwitch: 1;
unsigned kitchenLightSwitch: 1;
unsigned garageLightSwitch: 1;

1. subclass NSApplication
2. Don’t call NSApplicationMain
3. Do create an instead of my overridden (is that a word) MyApplication class
4. Call myApp.run()

I’m not sure what all NSApplicationMain does, but I figure whatever it does I can do myself.

I always thought nib stood for Next Interface Builder. Maybe that’s why you don’t like nibs. But seriously this is a good topic. I do all of my Java Swing work very well entirely in code - and it’s nice to know what you’re doing and where everything is. So knowing how to create interfaces dynamically is cool. Think: SmallTalk and Squeak.

That being said, I’m enjoying reading about your investigations into the nether regions of Cocoa. Be careful out there!

I still can’t decide whether it’s really that important to me to not use a nib, but at any rate I’m glad to be able to do it. Looking forward to your tackling the “could not connect the action…” messages.

Also, Interface Builder’s user interface is not always the most pleasant, ironically.

http://www.cocoabuilder.com/archive/message/cocoa/2003/12/31/84618

Text

You want to give your section a minimum margin, and you want to give your paragraph a minimum margin, but you don’t want a huge margin at the beginning of a section if it happens to start with a paragraph (instead of, say, a table).

Note: If the tags above got treated as markup, the example is:

<section>
<p>Text</p>
</section>

So that truly wasn’t intentional, but incredibly ironic. I was sure I closed my italic tags.

You closed and then opened one. I’ll just leave it, unless something bad happens.

That’s a rather brilliant strategy. Apple could simple buy a small township. Must be cheaper than all of the legal stuff.

I know the one you mean, but of course you can’t trademark names that are geographical locations.

What, you’ve never heard of iPhone, Alaska?

Mind fixing that for me?

I promised not to edit comments. However, (1) I’m a liar, and (2) unmatched tags are generally a bad thing.