This is a bug that has been around for a little while. Imagine you have a KryptonLabel inside a TableLayoutPanel and then set the TableLayoutPanel to be have transparent background. What you should see is the background from behind the table panel drawn as the background of the KryptonLabel.
Sadly this was not happening correctly. Most developers would not notice the issue because they have a solid color as the main background but if you have a gradient fill then you can clearly see the drawing problem.
This problem was not unique to the KryptonLabel but in fact present with any Krypton control that needs to draw some of its background as transparent. It is also exhibited not just when inside a TableLayoutPanel but for any control that can have a transparent background color defined, such as a regular Panel.
I won’t bore you with the tricky details of how the code solves the problem, suffice it to say it involves creating regions and adjusting them for the device content to ensure the drawing occurs in the correct location with correct clipping. Not many lines of code but a real pain to get just right in all circumstances.
To show it works here is an example. You can see below at design time a TableLayoutPanel is placed onto the gradient background. In the left cell of the table is a KryptonHeaderGroup that contains a KryptonPanel that itself contains a KryptonButton and KryptonLabel. The group and panel have been customized to have transparent backgrounds. The right cell contains a button and a couple of labels inside a traditional windows Group instance.

At runtime it works as expected with the main background showing through as required.

June 1st, 2007 at 5:25 pm
Dude, nice work
June 1st, 2007 at 6:54 pm
Great !
A million thanks for this fix, this will let us improve our UI using gradient shapes and Label.
Also, you really show to everybody how professional you are by giving such quick solutions to any bug or how you listen to your customers (for new features and so…).
Thank you for that!
June 1st, 2007 at 11:19 pm
I guess I am dense but I do not see any fix here ?
is there some code to download to fix this ?
June 2nd, 2007 at 12:41 pm
Denny,
I should have shown a ‘before’ picture that would have shown how it was wrong in the first place. Both of the pictures in the above blog entry have the problem corrected. The fix is code inside the Toolkit code and so you will have to wait until the next release in order to take advantage of it.
Phil
June 19th, 2007 at 11:13 pm
I’m struggling with this issue myself. When’s the next version of the toolkit scheduled for release?
June 19th, 2007 at 11:31 pm
When do you expect he next release of the toolkit? We’ve been using KryptonLabel consitently, and it would suck having to go back to normal labels.
June 20th, 2007 at 12:22 pm
Not sure when the next release will be. I hope to have a Beta of it out the door around the end of July or start of August.