• 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: drawRect not always called after setNeedsDisplay
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: drawRect not always called after setNeedsDisplay


  • Subject: Re: drawRect not always called after setNeedsDisplay
  • From: purple nekko <email@hidden>
  • Date: Wed, 20 Jul 2005 21:49:31 -0700

I already tried that.  No luck. The subview's drawRect method is still
not called.  Thank you for the suggestion though.

On 7/20/05, Ian was here <email@hidden> wrote:
> You could test this by calling display: in viewB
> rather than setNeedsDisplay:YES. This should call
> viewB's drawRect method sooner.  Then put a breakpoint
> or tracer within viewB's drawRect: method.
>
> If nothing else, this may help in revealing the
> problem.
>
>
>
>
> --- purple nekko <email@hidden> wrote:
>
> > Overview
> > ---------
> > I have an NSView (viewA) that manages multiple
> > subviews.  This view's
> > drawRect contains code that positions and sizes all
> > of its subviews
> > accordingly and calls each of the subview's
> > setNeedsDisplay:YES
> > method.  One of the subviews is also an NSView
> > (viewB), and it also
> > has multiple subviews.
> >
> > Problem
> > -------
> > If the window that contains viewA is resized,
> > viewA's drawRect method
> > is invoked, but for some unknown reason, viewB's
> > drawRect method is
> > not always invoked, despite the fact that viewA's
> > drawRect method
> > invokes viewB's setNeedsDisplay:YES method.  The
> > drawRect method
> > associated with all of viewA's other subviews are
> > invoked though.
> >
> > Question
> > --------
> > Can anyone suggest any reasons as to why viewB's
> > drawRect method is
> > not always called after its superview sends it a
> > setNeedsDisplay
> > message?  Any ideas on what I'm doing wrong would be
> > appreciated.
> >  _______________________________________________
> > 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
> >
>
>
>
>
> ____________________________________________________
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
>
>
 _______________________________________________
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: 
 >drawRect not always called after setNeedsDisplay (From: purple nekko <email@hidden>)
 >Re: drawRect not always called after setNeedsDisplay (From: Ian was here <email@hidden>)

  • Prev by Date: Re: NSFileManager - "Can't read ..." - Strange update
  • Next by Date: Re: view drawRect / setNeedsDisplay
  • Previous by thread: Re: drawRect not always called after setNeedsDisplay
  • Next by thread: Re: drawRect not always called after setNeedsDisplay
  • Index(es):
    • Date
    • Thread