I experimented with both complete containment and non-containment to eliminate parenting as the issue. Neither state makes a difference. I reversed the control order (put the BevelButton on top of the other object) to see if that would miraculously make a difference and it did not.
I have also now tested this in Windows (2000 in VirtualPC) and both a project built in 5.5.5 and an application compiled with 2K6R4 demonstrate the same problem. Turning Composite on in the Mac version does alleviate the problem on the Mac, but not in Windows (and I really don't like using Composite windows in RB). Having now implemented Karen's suggestion, I agree that it works very nicely. Thanks again Karen and I'm sorry I didn't get it when I read it in your original post. On 9/5/06, Joe Huber <[EMAIL PROTECTED]> wrote:
At 4:14 PM +0100 9/5/06, Narinder Chandi wrote: >I >have 2 separate BevelButtons with StaticText over each on the same window >but only one is exhibiting the problem. Investigating further, I found that >RB was not honouring the control order, i.e. the text was on top but was >being drawn behind. Parenting by Overlapification requires not only that the child has a higher position in the control order, but also that the child fit completely within the bounds of the parent at design time in the IDE. Any chance that one of the statictexts isn't completely within the bounds of its intended parent bevelbutton? BTW Karen's solution is a lot safer in any case.
_______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
