Page 1 of 1

Mostly Empty Window

Posted: 16 Nov 2025 23:45
by phred
Using 28.00.0500 on Win10

I dug my rarely used ThinkPad laptop out of its cabinet to update everything on it. Everything went well except for XY. I updated it from the 32bit to 64bit using the update process that showed up when XY was launched. Everything seemed fine for the rest of the session which lasted about four hours. The laptop had been restated a number of times along with being powered off and back on. All was fine yesterday.

Now when the laptop boots or is awakened from hibernation, XP looks like this:
2025-11-16_17-15-15.jpg
2025-11-16_17-15-15.jpg (196.24 KiB) Viewed 258 times
After playing around with a few things I discovered that if I use dual pane (which I rarely do) the data is visible. And if I then close the second pane, all is well and it looks like this:
2025-11-16_17-29-00.jpg
2025-11-16_17-29-00.jpg (79.52 KiB) Viewed 258 times
And as long as XY is not closed it's fine until the next time the laptop is shutdown or put to sleep.

Would anyone like to take a guess as to what is going on here?

EDIT: typo

Re: Mostly Empty Window

Posted: 17 Nov 2025 08:48
by admin
Crass. But cannot reproduce here.

Re: Mostly Empty Window

Posted: 17 Nov 2025 14:01
by phred
admin wrote: 17 Nov 2025 08:48 Crass. But cannot reproduce here.
I was fairly certain it wouldn't be. I forgot to see if I could reproduce it with a fresh instance butt will get to it at some point today and report back.

Re: Mostly Empty Window

Posted: 17 Nov 2025 18:24
by phred
It could be a few days before I can test a fresh instance and to keep digging into this. The laptop has been commandeered by my son for a while. <sigh>

Re: Mostly Empty Window

Posted: 17 Nov 2025 18:31
by admin
No problem, I can keep myself busy that long. :)

Re: Mostly Empty Window

Posted: 17 Nov 2025 18:37
by phred
:beer: :beer: :beer: ?

Re: Mostly Empty Window

Posted: 17 Nov 2025 20:07
by admin
:tup:

Re: Mostly Empty Window

Posted: 18 Nov 2025 04:51
by phred
I stole my laptop back from my son for an hour and I couldn't reproduce the initial issue. Reboot after reboot. All was/is well.

Should it rear its ugly head again, I'll reply to this thread.