Adding PREEVAL o:ClipChildren := .T.
Posted: Fri Dec 04, 2015 10:44 am
To make the HILITEGETS GRA_CLR_BLUE clause work properly in Xbase 2.0 under these conditions:
objects displayed in a DCGROUPBOX
themes enabled on a DCTABPAGE
XBPSYSCLR_TRANSPARENT is in use
There currently is a bug in Xbase 2.0. This causes the invalidaterect() method to not work properly.
In 1.9, I overload the default Express++ code that removes the HILITEGETS.
If you are using themes, the default Express++ code removes it by display a GRA_CLR_BACKGROUND line over the original blue line. This, when using themes leaves a light trace on the screen as it is not the same color. I use code from the Xbase++ help file for invalidaterect() to cause the box to be repainted, removing the highlight.
In Xbase 2.0, Alaska is providing a workaround to by setting in the PREEVAL clause the parent of the groupbox's clipChildren instance variable to .T.
I can manually add code to my programs to do this, in about 4-500 places or more. Is there any easier way to make this change for only specific instances. The reason is this may be a temporary workaround once they fix the problem.
Cliff
objects displayed in a DCGROUPBOX
themes enabled on a DCTABPAGE
XBPSYSCLR_TRANSPARENT is in use
There currently is a bug in Xbase 2.0. This causes the invalidaterect() method to not work properly.
In 1.9, I overload the default Express++ code that removes the HILITEGETS.
If you are using themes, the default Express++ code removes it by display a GRA_CLR_BACKGROUND line over the original blue line. This, when using themes leaves a light trace on the screen as it is not the same color. I use code from the Xbase++ help file for invalidaterect() to cause the box to be repainted, removing the highlight.
In Xbase 2.0, Alaska is providing a workaround to by setting in the PREEVAL clause the parent of the groupbox's clipChildren instance variable to .T.
I can manually add code to my programs to do this, in about 4-500 places or more. Is there any easier way to make this change for only specific instances. The reason is this may be a temporary workaround once they fix the problem.
Cliff