Click here to Skip to main content
15,881,413 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
Some textboxes are not affected. Anybody have an idea how to fix this?


Visual Studio 2017 textbox bug? - Album on Imgur[^]

What I have tried:

I've tried checking/comparing the properties of both textboxes shown in the link but they're all the same.
Posted
Updated 13-Jun-18 16:41pm
Comments
Maciej Los 14-Jun-18 4:07am    
Without seeing your code, no one is able to guess why it happens...
Richard Deeming 14-Jun-18 12:00pm    
It almost looks like you've got another control - either a TextBlock or Label - placed on top of the first TextBox. Maybe you're using a Grid layout, and haven't set the Grid.Row and Grid.Column correctly on one of the child controls.

But as Maciej said, without seeing the relevant parts of your code, we're just guessing blindly.

Click the green "Improve question" link and update your question with the relevant parts of your XAML.

1 solution

If this is just the standard TextBox and you didn't create your own or add your own painting code, it's not a bug in the TextBox.

This looks more like a problem with your video card driver.
 
Share this answer
 
Comments
[no name] 13-Jun-18 22:49pm    
It's a regular TextBox. I'm using a WPF. If it's with my video card driver, why is it that other TextBoxes aren't affected?
Dave Kreskowiak 14-Jun-18 9:04am    
I'm not going to go into a huge explanation. Suffice it to say that WPF will use DirectX to handle rendering if it's available. The standard Windows Common Controls will not use DirectX.

In WPF, it's NOT a regular TextBox out of the Common Controls library like what WinForms uses. It's a "simulation" of one.

Most rendering problems can be fixed by an updated video driver.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900