• 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: NSProgressIndicator -setFrameOrigin visual updating anomaly
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSProgressIndicator -setFrameOrigin visual updating anomaly


  • Subject: Re: NSProgressIndicator -setFrameOrigin visual updating anomaly
  • From: Nathan Day <email@hidden>
  • Date: Sun, 12 May 2002 20:56:25 +0930

I don't know if this will fix your problem but have you tried removing the NSProgressIndicator from the view hierarchy and then latter reinserting it, instead of moving it. Since a view stores it position within its container view its quite easy to do, you just have to make sure you retain it before removing it. I've done this and I don't get the problem you are talking about. Hiding a view but still leaving it within the view hierarchy can cause some problems, since it still active. For example a user can press tab to select a hidden view.

On Sunday, May 12, 2002, at 04:08 PM, Matt Gemmell wrote:

I have an NSProgressIndicator which I only want to be visible during a
certain operation. Since NSProgressIndicator isn't an NSControl (it's an
NSView), I can't just use -setVisible: to make it invisible until the
appropriate time. Instead, I decided to use -setFrameOrigin: to move it
outwith the visible portion of the window until such times as I need it.
I'd welcome a better solution, but that's not really my question.

In my NSDocument subclass (this is a standard Cocoa document-based app),
I implement awakeFromNib: and move the progress indicator at that time.
This works fine, but it leaves the other controls looking slightly
strange - their blue tint has gone. Checked checkboxes and selected
radiobuttons lose their blue tint until they're clicked on again or
tabbed into. They don't appear 'disabled'; they just don't have the blue
tint anymore.

It doesn't affect functionality in any way, but it looks odd, and I'd
like to know what's causing it and how I can fix it. Any ideas?
_______________________________________________
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: NSProgressIndicator -setFrameOrigin visual updating anomaly
      • From: Matt Gemmell <email@hidden>
  • Prev by Date: Re: Super's Super?
  • Next by Date: Re: NSProgressIndicator -setFrameOrigin visual updating anomaly
  • Previous by thread: NSProgressIndicator -setFrameOrigin visual updating anomaly
  • Next by thread: Re: NSProgressIndicator -setFrameOrigin visual updating anomaly
  • Index(es):
    • Date
    • Thread