Re[2]: Hidden NSSlider

FROM : Lance Drake
DATE : Thu Apr 07 02:06:32 2005

> Click and hold the slider (in IB)until it gets a deeper shadow, then 
> drop where you want it. Same thing works if you accidentally cover a 
> UI element with a tabview or a box and you want to put it inside that 
> view instead of under it.
> -Daniel DeCovnick
> danhd123 at mac dot com
> Softyards Software


Hi Dan,
   
   Good... a way to use the IB tool to get it done.  Actually, I filed a 
bug that makes note of the fact that Interface Builder stacks thing in 
a reverse manner..  (Bug# 3565539 See description below.)  Also, I was 
under the impression that the question related to a problem encountered 
at runtime.  In any event, it looks like the bases are well covered.

Best Regards,

Lance Drake

------------------------------------------------------------------------
-----------
20-Feb-2004 01:14 PM Lance Drake:
* SUMMARY
Moving objects in a NIB to physically be 'In Front' causes them to be 
logically 'In Back'

* STEPS TO REPRODUCE
1. Open an application NIB, add an NSQuickDrawView, then an NSButton 
into a window
2. Position the button to be on top of the NSQuickDrawView area.
3. Observe the list mode of the Window object - Notice, in that list 
where the NSQuickDraw view is in relation to the NSButton
5. Go back to the window view,select the NSQuickDrawView object and 
reverse the layering order by way of the menu (Move to front/back)
6. Go back to the list of objects in the window and notice that the 
NSButton is in the reverse position to the NSQuickDrawView item from 
where it was.
7. Build the app - see the window - observe that when the Button is 
viewed in the NIB as being in FRONT of the NSQuickDrawView that it is 
not visible but that when the NSButton is shown as being BEHIND the 
NSQuickDrawView, then it is visible.

* RESULTS
When you specify an object be at the rear of the view, it is placed at 
the TOP of the list of items in the List - and will overdraw anything 
below it on that list.  The higher items in that list are the LAST to 
be drawn and, as such, as not BEHIND anything that is lower on the 
list.  The lowest items are the FIRST to be drawn.  The bug is that 
what you see in the NIB window is not what gets rendered in the NIB 
hierarchy.