We had a major storm through here recently and we suffered damage to the house roof and ceilings. I just received the quote to repair. I’m hoping that a small fraction of the 80,000 odd people that download SDIO and/or Desktop Info every month won’t mind chipping in a few dollars to help out. Click on the big blue button at the bottom of the page to help us keep a roof over our heads, literally!
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
Morning Glenn,
We're finding great improvements in regards to display change and hyperlinks - many thanks.
We only found one display bug, where a USB-C external monitor was the primary display, aftre unplugging DTI didn't failback to the laptop display.
Anyway, on to the bug at hand...
We've always been launching via a scheduled task, which hasn't changed (other than the target exe name with the latest version).
However, with this version, we're now seeing an exception error (attached). Sometimes this error is in the foreground (attached), sometimes it's not visible. We find in either scenario, it causes DTI to be visible on the taskbar.
Many thanks as always!
Thanks for the bug report.
Can you run the scheduled task manually?
I just tested that here and it worked perfectly. Check your ini file options for monitor-mode.We're finding great improvements in regards to display change and hyperlinks - many thanks.
We only found one display bug, where a USB-C external monitor was the primary display, aftre unplugging DTI didn't failback to the laptop display.
Afternoon Glenn,
Apologies for the delay, I found the cause...
It seems something in the changes requires the taskbar to be loaded prior to DTI, which it seems may not have been the case before.
Anyway, once I finally determined that to be the cause, adding a 3 seconds wait to the scheduled task has done the trick.
Our ini doesn't include monitor-mode, should I consider adding it?
Thanks
That's entirely feasible. The code that handles the taskbar probably doesn't handle the taskbar not being there. I added an exception wrapper around that code in v3.18.1. Did you test that?
As for monitor mode, the default behaviour is single monitor mode so you shouldn't need to add it. However it might be worth it for the exercise to see if it changes anything.
Afternoon Gelnn,
Apologies, I hadn't spotted the newer release.
18.1 looks more promising for the taskbar issue, probably needs a little more testing...
monitor-mode didn't help with the display disconnection bug, after unplugging the primary monicor (USB-C) the DTI process continued running but wasn't visible/ didn't failback to the laptop display which had become primary.
Thanks
I'd be curious to now if the Windows Display Settings still shows the two monitors after the disconnection.
Afternoon Glenn,
I've tested both v18.1 & 19 for these bugs...
In terms of the taskbar/ error, both have certainly been better!
Though, I find say 1 in 10 logins, DTI will display on the taskbar.
However, there's no longer a visible error - I presume there is an error somewhere (possibly the same one) it's just not visible.
Nothing happens is you click DTI on the taskbar, and of course, DTI closes if a user closes the taskbar.
After unplugging the primary monitor where DTI didn't failback, I can confirm Windows settings no longer shows another monitor connected. Additionally, items on the desktop had reverted to the laptop display from the disconnected monitor.
It might be worth mentioning, I left the DTI task running, and reconnected the USB-C monitor - DTI didn't reappear on it (so it was running but not visible on any monitor).
Hi Glenn,
I set the task to run with debug log file argument.
However, there weren't any errors or warnings that stood out to me.
The DTI icon was visible on the taskbar from when it first launched, and I had deleted the log file prior to capturing the logs with the issue.
failed to upload log as text file.
you'll need to zip it.
