• 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
is [uiObject display] necessary ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

is [uiObject display] necessary ?


  • Subject: is [uiObject display] necessary ?
  • From: Jens Bauer <email@hidden>
  • Date: Wed, 5 Dec 2001 11:04:47 +0100

Hi all,

I'd like to know if there is any reason for [object display]; in
situations like these...

[message setStringValue:@"Some string"];
[message display];

[progressIndicator incrementBy:stepSize];
[progressIndicator display];

[quitButton setKeyEquivalent:@"\n"];
[quitButton setEnabled:NSOnState];
[quitButton display];

[cancelButton setKeyEquivalent:@""]; /* changes from @"\e" to nothing */
[cancelButton display]; /* In fact, I don't think this
behaves correctly. */

[icon setImage[NSImage imageNamed:@"Yep"]]];
[icon display];

The reason I ask, is that I was sure I've seen it somewhere. It could be
that I confused
this with a Carbon example (which is most likely the case; Converter).

Are there any issues with older versions of the user-interface objects,
where you need
to redraw after a change ?


Love,
Jens

--
Just in case you like Opera... We'll make it even better!

------------------ RFC822 Header Follows ------------------

  • Follow-Ups:
    • Re: is [uiObject display] necessary?
      • From: jgo <email@hidden>
    • Re: is [uiObject display] necessary ?
      • From: John Hörnkvist <email@hidden>
  • Prev by Date: Forcing small text to be anti-aliased
  • Next by Date: Re: [ANN] OCUnit: Unit Testing Objective C code on Mac OS X
  • Previous by thread: Forcing small text to be anti-aliased
  • Next by thread: Re: is [uiObject display] necessary ?
  • Index(es):
    • Date
    • Thread