• 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: Resizing Columns
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Resizing Columns


  • Subject: Re: Resizing Columns
  • From: Thomas Davie <email@hidden>
  • Date: Fri, 10 Jun 2005 22:08:47 +0100

It appears that if I add
NSLog (@"{%f,%f,%f,%f}", aRect.origin.x, aRect.origin.y, aRect.size.width, aRect.size.height);
in the selection code it all works...



This symptom (adding a print statement makes a bug go away) is often indicative of a memory problem - e.g. an array overstepping its bounds, or a function that is not returning the type it is supposed to. Examine your code more closely (it isn't necessarily in the immediate neighbourhood of where you put the NSLog statement), turn on all warnings (-Wall) or try using a tool like 'lint' (I don't know if there is a version that will handle Obj-C).

That's what I thought too... -Wall is on as is raising errors instead of warnings. Using NSZombieEnabled revealed nothing (no messages at all)... All very odd.


Bob
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Resizing Columns (From: Thomas Davie <email@hidden>)
 >Re: Resizing Columns (From: Thomas Davie <email@hidden>)
 >Re: Resizing Columns (From: Cameron Hayne <email@hidden>)

  • Prev by Date: Re: Am I overreleasing something?
  • Next by Date: Re: Am I overreleasing something?
  • Previous by thread: Re: Resizing Columns
  • Next by thread: NSTextTable/NSDrawer bug?
  • Index(es):
    • Date
    • Thread