Screen layout issue with 2018.7

[BRoberson]

Yes. I uninstalled it through settings. After checking it found an older version, 2016.45. Uninstalled that one then did a restart. No xlight ref was in program files etc. Then did the new v7 install.

[Gilrock]

Personally I don't believe uninstalling fixes anything.  Also there is really no reason you can't have several versions of xLights.  During the install I just type in the version number to be the install folder so I end up with many versions and I can easily launch an older version if I need to compare behavior.

[Gilrock]

By the way I just tried 2018.7 and I have the same issue.   My Layout screen won't refresh so I'd just go back to 2018.6 until we report a fix.

[BRoberson]

Ok will do Thanks again.

Cheers

[dkulp]

By the way I just tried 2018.7 and I have the same issue.   My Layout screen won't refresh so I'd just go back to 2018.6 until we report a fix.

Gil, can you try with the code I checked in this afternoon?   Looking at the log, the line that stood out was:

Code: [Select]

panel - glVer:  4.5.0 - Build 22.20.16.4749  (Intel(R) HD Graphics 520)(Intel)
whereas the other contexts look like:

Code: [Select]

Layout - glVer:  3.3.0 - Build 22.20.16.4749  (Intel(R) HD Graphics 520)(Intel)
I'm not sure if the non-core profile of the first one is causing issues creating the others.  Anyway I checked in some fixes to make sure all the contexts are created the same. 

[Gilrock]

Yeah I already had tried pulling in your change.  Mine seems worse than what they are reporting.  All my GL windows are not drawing except for 1...the House Preview.  Here's a snippet from my log:

2018-03-12 18:56:04,491 66652 log_base [DEBUG] Viewing log file C:\Users\Gil\AppData\Roaming/xLights_l4cpp.log.
2018-03-12 18:56:15,214 66652 log_opengl [INFO] Layout - glVer:  3.3.0 NVIDIA 388.13  (GeForce GTX 780 Ti/PCIe/SSE2)(NVIDIA Corporation)
2018-03-12 18:56:15,214 66652 log_opengl [INFO] Try creating 3.3 Cache
2018-03-12 18:56:17,275 66652 log_base [DEBUG] Viewing log file C:\Users\Gil\AppData\Roaming/xLights_l4cpp.log.
2018-03-12 18:56:28,230 66652 log_base [DEBUG] xLightsFrame::ShowHideAllSequencerWindows
2018-03-12 18:56:28,230 66652 log_base [DEBUG] xLightsFrame::ShowHideAllSequencerWindows - show
2018-03-12 18:56:28,679 66652 log_opengl [INFO] Preview - glVer:  3.3.0 NVIDIA 388.13  (GeForce GTX 780 Ti/PCIe/SSE2)(NVIDIA Corporation)
2018-03-12 18:56:28,679 66652 log_opengl [INFO] Try creating 3.3 Cache
2018-03-12 18:56:28,895 66652 log_opengl [INFO] WaveForm - glVer:  3.3.0 NVIDIA 388.13  (GeForce GTX 780 Ti/PCIe/SSE2)(NVIDIA Corporation)
2018-03-12 18:56:28,895 66652 log_opengl [INFO] Try creating 3.3 Cache
2018-03-12 18:56:28,906 66652 log_opengl [INFO] EffectGrid - glVer:  3.3.0 NVIDIA 388.13  (GeForce GTX 780 Ti/PCIe/SSE2)(NVIDIA Corporation)
2018-03-12 18:56:28,906 66652 log_opengl [INFO] Try creating 3.3 Cache
2018-03-12 18:56:28,965 66652 log_opengl [INFO] TimeDisplay - glVer:  3.3.0 NVIDIA 388.13  (GeForce GTX 780 Ti/PCIe/SSE2)(NVIDIA Corporation)
2018-03-12 18:56:28,965 66652 log_opengl [INFO] Try creating 3.3 Cache
2018-03-12 18:56:29,064 66652 log_opengl [INFO] ModelPreview - glVer:  3.3.0 NVIDIA 388.13  (GeForce GTX 780 Ti/PCIe/SSE2)(NVIDIA Corporation)
2018-03-12 18:56:29,064 66652 log_opengl [INFO] Try creating 3.3 Cache
2018-03-12 18:56:48,698 66652 log_base [DEBUG] Closing sequence.

[Gilrock]

Ok I just found a temporary workaround.  If I grab the corner of the application and resize it the GL windows start working but I had to do it every time I switch away from a tab and come back.

[Gilrock]

It appears to not be updating until it hits the Render called by a paint event.  When we force call an update to the other render calls its not drawing unless the paint render has been called.

[Gilrock]

I circled some other drawing anomalies I'm seeing:

[Gilrock]

I found a workaround.  It seems to fix it if you run the application in compatibility mode for Windows 7 or 8.

Is this problem happening for anyone not using Windows 10?

BTW if anyone is using Windows 10 and doesn't have the issue we don't need to know.