WPF TextBox caret and regions comparaison
Hi, I'm getting test errors when comparing 2 pictures of the same TextBox, because of the blinking caret: sometimes visible, sometimes not... I didn't found any solution to hide it on the app s...
Forum Discussion
Hi Yoann,
Well... To say the truth, I'm really doubting that the code will be that fast that it will be able recognize that the caret is not displayed and take a screenshot before it is shown again.
One more question - why do you need to compare images?
The overall experience is that image comparison is the option that should be used as the last resort when nothing else is working. The reason for this is that usually the image comparison works acceptably well only on the computer it was initially implemented at. And it stops working when you execute the same code on another box. Usually this happens because another box has different OS, with different color scheme and color depth, etc.
Why not to use Property Checkpoint and use the text and/or other text box properties that are stable and do not depend on OS, color, etc. ?
Well... To say the truth, I'm really doubting that the code will be that fast that it will be able recognize that the caret is not displayed and take a screenshot before it is shown again.
One more question - why do you need to compare images?
The overall experience is that image comparison is the option that should be used as the last resort when nothing else is working. The reason for this is that usually the image comparison works acceptably well only on the computer it was initially implemented at. And it stops working when you execute the same code on another box. Usually this happens because another box has different OS, with different color scheme and color depth, etc.
Why not to use Property Checkpoint and use the text and/or other text box properties that are stable and do not depend on OS, color, etc. ?
