• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: bug in AddressBook Framework headers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bug in AddressBook Framework headers


  • Subject: Re: bug in AddressBook Framework headers
  • From: Karl Kuehn <email@hidden>
  • Date: Mon, 17 Feb 2003 11:11:28 -0500

Thanks for the reply. I can see how this is not a bug... it is a bit misleading. Having separate names for kABICQHomeLabel and kABMSNHomeLabel elements is not intuitive. Why not just us the generic kABWorkLabel and kABHomeLabel? The current method is very anti-intuitive. My request would go to simplifying this one.

And while I have you on the line... I am having trouble with the ABLocalizedPropertyOrLabel function. I can compile it into Obj-C executables, but I am trying to work it into a Obj-C++ (.mm) project and it keeps blowing up at me with the message:

ld: warning prebinding disabled because of undefined symbols
ld: Undefined symbols:
ABLocalizedPropertyOrLabel(NSString*)

I have created a trivial case, and when the file ends in .m it compiles and runs fine. If I simply change the name to end in .mm and clean the target then I get that compilation error. Any thoughts on how I can get around this? My current method is to write my own function to take it's place... but I prefer not to re-invent the wheel every time... Am I missing something again?

Karl Kuehn
email@hidden

On Sunday, February 16, 2003, at 06:20 PM, Henri Lamiraux wrote:

You are not correct in your assessment. There is no bug there. Home is home for whatever type of property. What is different between ICQ and AIM is the property (kABICQInstantProperty vs kABAIMInstantProperty). A label should always be associated with the property it is coming from. Don't forget that a user can use any labels he/she wants. I can create a card in AddressBook with the label "Vacation Home" for a phone, email, street address, etc... What is important is the > property.

As I said in my previous email you won't be able to distinguish between two different customs label (e.g. "Vacation Home"). Whatever your app is trying to do won't work in most cases.....
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: bug in AddressBook Framework headers
      • From: Vince DeMarco <email@hidden>
References: 
 >Re: bug in AddressBook Framework headers (From: Henri Lamiraux <email@hidden>)

  • Prev by Date: NSButton over NSImageView
  • Next by Date: Re: immutable NSMutableDictionary
  • Previous by thread: Re: bug in AddressBook Framework headers
  • Next by thread: Re: bug in AddressBook Framework headers
  • Index(es):
    • Date
    • Thread