GUIDarkTheme UDF

[argumentum]

hmm, reboot and test again. Not to turn a blind eye to the issue but to troubleshoot it.
Since all this is event driven, you'd have to "activate the child GUI or click on it with the mouse" to create an event.
So, rebooting shows if the OS is resource starved ( to give it a name ) or not.
In either case it could use some rethinking/pondering but the reboot is a good "retry" to look at what is causing the event/"white line" 🤯

[WildByDesign]

5 hours ago, bladem2003 said:

The white line remains until I activate the child GUI or click on it with the mouse.

This usually happens when the child GUI is shown with @SW_SHOWNA.

I have a fix for this now. I will put together a release in this morning.

[WildByDesign]

GUIDarkTheme 3.1.1

• Added basic context menu to the Demo
• Fixed text color and focus rectangle for SysLink controls
• Fixed issue with menubar painting when GUI has one or more child GUI

Latest download available in the first post of the topic.

 

@bladem2003 Please let me know if this resolves your issue with painting of the white line.

[bladem2003]

37 minutes ago, WildByDesign said:

@bladem2003 Please let me know if this resolves your issue with painting of the white line.

It looks like the devilish white line has disappeared.

[jpm]

Hi,

why the split button disabled have a vertical bar highlighted?

The 3.1.1 need #forceref $iD, $pData and Local $hDC, $hBresh defined before Switch

[WildByDesign]

9 hours ago, jpm said:

why the split button disabled have a vertical bar highlighted?

I had a look in the theme resources and this seems to be a Microsoft bug in their theme files. I think that the only way that I can fix that vertical bar highlight issue is by subclassing the splitbutton control. This will take some time but I will see how easy or difficult it is to fix.

9 hours ago, jpm said:

The 3.1.1 need #forceref $iD, $pData and Local $hDC, $hBresh defined before Switch

Thank you for letting me know. I will have this fixed in the next release.

I have added the AutoIt3Wrapper_Au3Check_Parameters back into my testing script so that I do not miss these again.