Dark Scheme pop-ups unreadable in 2026 R1

Toad for Oracle & DevOps Toolkit
1

When any Dark Scheme is applied, pop-up text is white and unreadable against the white pop-up background. This is not an issue in 17.1. Other versions were not tested.

Example 1: Find All (keyword) when "Display count after find all" is checked

image
image362×295 6.26 KB

Example 2: In Export DDL, add some objects then remove them

image
image384×256 21.8 KB

Example 3: Help -> Licensing

image
image805×567 56.6 KB

2

Yeah, there are issues with such things. Here is our licensing dialog:

image
image1200×900 31.8 KB

But, our Find all works fine (Cobalt theme):

image
image543×234 7.78 KB

Also get a valid, dark mode result with Export DDL work flow.

Cheers,
Russ

3

@russell.cannon - Licensing has been fixed for 2026 R2. The fix is in the current beta.

@philip.kwan - I see no problems with the Find All dialogs in 2026 R1. Which theme are you using? I tried Cobalt.

Michael

4

@mstaszew It happens for every Dark theme. I suspect it may have something to do with running in Compatibility Mode for Windows 7. Unfortunately I have to run it this way otherwise it crashes in my company's VDI.

5

I tried with Windows 7 compatibility mode and I do see differences, but the text is still legible. I see white dialog background and black text as you see in 17.1. John Dorlon may need to step in on this one when he's in the office.

Do you recall what kind of crash you saw when you disable compatibility mode? What kind of VDI are you using and what is the OS? Toad should run normally in a virtual environment. I run Toad exclusively within VMWare and/or Azure VM and haven't needed to modify the compatibility mode.

Michael

6

I'm using Citrix VDI, the OS is Microsoft Windows [Version 10.0.17763.7922]. This is the error message.

image
image392×150 4.53 KB

Event Viewer displays this:
Faulting application name: Toad.exe, version: 26.1.193.8012, time stamp: 0x698e5200
Faulting module name: ReactiveClientLibrary.dll, version: 3.0.0.153, time stamp: 0x659ffedb
Exception code: 0xc0000005
Fault offset: 0x000000000000ead9
Faulting process id: 0x7644
Faulting application start time: 0x01dced255f089a0f
Faulting application path: C:\Program Files\Quest Software\Toad for Oracle 2026 R1 Edition\Toad for Oracle 26.1\Toad.exe
Faulting module path: C:\Program Files\Quest Software\Toad for Oracle 2026 R1 Edition\Toad for Oracle 26.1\ReactiveClientLibrary.dll
Report Id: 1e661045-f617-4720-b28c-e96956f1dc90

7

Hi Philip,

I probably can't do anything about the Dark Mode issues under Citrix VDI and compatibility mode enabled, but changing one or more of the settings below may allow you run without compatibility mode enabled, which I believe will solve your dark mode problem:

  1. Go to Toad Options. Select "Online and AI" on the left. Set "Toad Improvement Program" to "No". Restart Toad and try with compatibility turned off. If that doesn't help, move on to step 2.
  2. Go to Toad Options. Select "Online and AI" on the left. Uncheck "Allow Internet Access" (this will not affect your ability to connect to any database, it's just for Toad's internal "phone home" type stuff). Restart Toad and try with compatibility turned off. If that doesn't help, move on to step 3.
  3. With Toad shut down, edit the file Toad.ini with notepad. Add these lines under [SETTINGS]
dxUIAutomationEnabled=0
VSTUIAccessibilityEnabled=0

Toad.ini is in the folder %APPDATA%\Quest Software\Toad for Oracle\<version number>\User Files\

Please let me know if that helps.

8

Hi John,

The good news is I am now running Toad without compatibility mode enabled (after going through all 3 steps). The bad news is my original issue is still here, i.e. pop-ups having a white background in Dark Mode which makes text unreadable. I've tried changing from Dark to Light Mode, disabling and re-enabling Color Schemes, and switching between various Dark Schemes but the end result is still the same.

The puzzling thing is that it works fine in 17.1 but not 2026 R1.

9

2026R1 uses the same call to show those popup messages as 17.1, so I'm not sure what's changed.

I did some googling and found the following. I know you are using Citrix, but is it Citrix Workspace App or do you have this setting in your environment somewhere?

Disable Hardware Acceleration/Font Smoothing: In Citrix Workspace App properties or within your session, disable "Use hardware acceleration" or ensure that "Legacy graphics mode" is toggled for compatibility if the app window remains entirely blank.

10

Well this is embarrassing but it turns out I still had compatibility mode enabled after step 3, so the fixes you suggested didn't actually help after all. I still can only run Toad in Windows 7 compatibility mode.

I am running Citrix Workspace App but there is no such property or setting as you mentioned.

I appreciate you looking into this but it's not a game-stopper, I can always just use Light Mode instead. I am curious about whether the license dialog fix might also fix this issue, though. Guess I'll have to wait for the next release to find out.

11

HI Philip,

The license dialog fix was specific to that window, so it won't help.

Here's another thing you can try, I don't know if it will help or not.

Go to Toad Options -> General. In the "Graphics" box, uncheck "Application DPI Awareness". Toad will need to restart after that.

12

John, I'm happy to report that this actually worked. Thank you so much!

Best regards,
Phil

13

Excellent! Did that allow you to run without compatibility mode or did it just solve the text problem?

14

It just solved the text problem. The compatibility mode issue might be security-related, I'll check with my company's IT security team next week.