[Support]

It's not a bug, you have placed the Bevel over buttons.

#42965

[HeDiBo]

QUOTE (Support @ Jul 19 2010, 03:04 PM) <{POST_SNAPBACK}>

It's not a bug, you have placed the Bevel over buttons. Bevels should get a lower z-order than the components they enclose automatically. Try it: you'll see that with standard components it's impossible to get them in the wrong z-order. Even if you say Bring To Front for a TBevel, it will still go below the enclosing components.

At least, that's what I experienced

#42968

Support

Keymaster

Sorry, but I meant BringToFront for buttons.
And I have checked this situation with standard controls before posting too.

Step 1. Place TSpeedButton on form
Step 2. Place TBevel over this button
Button will not be accessible in the design-time, even while TBevel is placed over him. <img src="style_emoticons//smile.gif” style=”vertical-align:middle” emoid=”:)” border=”0″ alt=”smile.gif” />

#42969

HeDiBo

Participant

QUOTE (Support @ Jul 19 2010, 03:24 PM)

Sorry, but I meant BringToFront for buttons.
And I have checked this situation with standard controls before posting too.

Step 1. Place TSpeedButton on form
Step 2. Place TBevel over this button
Button will not be accessible in the design-time, even while TBevel is placed over him. <img src="style_emoticons//smile.gif” style=”vertical-align:middle” emoid=”:)” border=”0″ alt=”smile.gif” />

That's true. But run that application. Now you can select and click the button!

Well, at least in my system I can. <img src="style_emoticons//wacko.gif” style=”vertical-align:middle” emoid=”:wacko:” border=”0″ alt=”wacko.gif” />

#42676

Support

Keymaster

Look on the attached project.
Part of button, which is under bevel, is not accessible. You have other result? %)

#42678

HeDiBo

Participant

QUOTE (Support @ Jul 19 2010, 03:42 PM) <{POST_SNAPBACK}>

Look on the attached project.
Part of button, which is under bevel, is not accessible. You have other result? %)

You're absolutely right

#42978

OldGrumpy

Participant

Hint: One does have a window handle, the other does not. I've had my share of headaches with the handle-less VCL controls

Author

Posts

[Support]

Sorry, but I meant BringToFront for buttons.
And I have checked this situation with standard controls before posting too.

Step 1. Place TSpeedButton on form
Step 2. Place TBevel over this button
Button will not be accessible in the design-time, even while TBevel is placed over him. <img src="style_emoticons//smile.gif” style=”vertical-align:middle” emoid=”:)” border=”0″ alt=”smile.gif” />

[HeDiBo]

QUOTE (Support @ Jul 19 2010, 03:24 PM)

Sorry, but I meant BringToFront for buttons.
And I have checked this situation with standard controls before posting too.

Step 1. Place TSpeedButton on form
Step 2. Place TBevel over this button
Button will not be accessible in the design-time, even while TBevel is placed over him. <img src="style_emoticons//smile.gif” style=”vertical-align:middle” emoid=”:)” border=”0″ alt=”smile.gif” />

That's true. But run that application. Now you can select and click the button!

Well, at least in my system I can. <img src="style_emoticons//wacko.gif” style=”vertical-align:middle” emoid=”:wacko:” border=”0″ alt=”wacko.gif” />

[Support]

Look on the attached project.
Part of button, which is under bevel, is not accessible. You have other result? %)

[HeDiBo]

QUOTE (Support @ Jul 19 2010, 03:42 PM) <{POST_SNAPBACK}>

Look on the attached project.
Part of button, which is under bevel, is not accessible. You have other result? %)

You're absolutely right

#42978

[OldGrumpy]

Hint: One does have a window handle, the other does not. I've had my share of headaches with the handle-less VCL controls

Author

Posts

[Author]

Posts