Hey John,
I am so grateful for your efforts trying to address this. It is much appreciated. I have always said that Quest has the best technical support in the industry–certainly light-years ahead of Oracle.
The most reliable way I can replicate the crash is using the describe window, and I just replicated it in 25.2. That version had another issue that made it unsuitable for our use, so we did not use it after it was installed and stuck with 25.1. That was the issue with the windows that kept appearing when connecting to and running queries in databases that were only mounted. We grabbed 25.3 right away and started using it because it fixed that issue.
That is in the VDI. I only have version 17.0 in my company laptop. That is the one that I reported is getting the McAfee file access protection warnings that we talked about. We still haven’t fixed that.
The narrator is definitely off in my VDI right now, but I see that “Allow the shortcut key to start Narrator” is box-checked. (now unchecked) Although that is a convoluted key sequence, I wonder if there is some way that that it is getting enabled without my realizing and then being disabled. I doubt it, but there it is.
I do know this. Narrator somehow got enabled on my company laptop a few months ago, and it started talking while I was away from my desk. I have no idea how that happened, but due to my worsening eyesight in my old age, I had enabled various accessibility features to assist me. I did not do that in the VDI though. All I did in there is forcing everything into dark mode and enlarging the mouse pointer. As far as I can remember, I never enabled Narrator in the VDI, and I have never found it to have been enabled unexpectedly. It is not enabled right now, but Toad still crashes.
I can modify the .inf file if that is what you want to do. What I cannot do either on my company laptop or the VDI is install a Beta version, so I will not be able to test a possible fix before it is released into the wild.
Cheers,
Russ
This morning I rebooted the VDI and confirmed that narrator was not enabled afterward. The Toad crash issue remained.
Cheers,
Russ
Ok, the fact that you can actually repro it in 25.2 is good news, because that's when this offending code was added to Toad. Maybe your other accessibility settings have enabled this code. I will add the code to disable it by an ini setting (which I'll post later).
In the meantime, we'll continue to try to get a VDI set up so we can actually reproduce the problem.
All I did in there is forcing everything into dark mode and enlarging the mouse pointer.
I've enlarged my mouse pointer to see if it would enable Toad's accessibility code but it did not. I already have windows in dark mode by this setting. Is that what you meant by "forcing everything into dark mode"?
Yeppers. I also use a dark theme in Toad.
In 26.1 you can add this line under [SETTINGS] in Toad.ini to disable the offending code (do this while Toad is NOT running)
VSTUIAccessibilityEnabled=0
You may also want to add this line (it disables similar code for other controls in Toad. Even if this code is not causing any problems, you may get a slight performance gain by disabling it too, which you might as well since narrator is off)
dxUIAutomationEnabled=0
There is no harm in adding these lines now. They should get carried from 25.3 to 26.1 with all of your other settings.
I will add them with the understanding that they will have no effect until 26.1. I am going to try to get approval for the beta. When will that show up in the beta?
Cheers,
Euss
Yes, I'll have it in beta starting Monday 1/19.
The 2nd one may actually have an effect now for 25.2 and 25.3. It would if you had narration enabled (it would cause narration for some controls to not happen)
1 Like
Does Toad have a way to edit Toad.ini within Toad?
No, but if you hold down SHIFT and go to main menu -> view -> Toad Options, then this dialog will appear:
If you click Yes, then Toad will close and Toad.ini will be opened in notepad for you.
So, that's handy.
Oh wow. Another thing I never knew about.
Cheers,
Russ
I think I added that for my own convenience.
There are a few other things like that. Right-click the "database" dropdown in the login window is another:
BTW: Is capitalization of parameter names in Toad.ini important or is it just for easier reading? Just wondering.
I cannot use Notepad because it is just too bright for my elderly eyes. I used Visual Studio Code instead.
Cheers,
Russ
Case does not matter.
Did you know you can put notepad in dark mode? At least in Windows 11 you can. Click the gear icon in the top right. Then "App theme", and set it to dark.
LOLs That is all very good for Win11, but it is not possible in our VDI O/S. You know how server O/Ss go. None of the “cool” features get into them.
In any event, I always use Notepad++ or Visual Studio Code.
Win11 is all the justification a person needs for switching to Linux. I am working on Fedora for my personal stuffs, but of course companies and the government are standardized on Windows mainly because of AD and GPOs.
Cheers,
Russ
I should probably change that from notepad to "your text editor"
1 Like
From an earlier post of yours:
If I just open a close a popup window, which I usually close by hitting ESC if there were no changes, over and over again, Toad does not crash. I have to have done something inside the window. In the case of Settings, I have to have clicked to a different category on the left. Just once is enough.
When I hit ESC, does that trigger the Cancel button or the X at the top right or does it do something something else?
Cheers,
Russ
I have answered my own question. ESC to exit appears to invoke the X at the top right. It is only the X and ESC that I can make crash Toad. The buttons don’t seem to have that effect. If I just use the button, it doesn’t crash.
Of course, the only way to close a describe window is either ESC or the X.
Now, let me throw this curveball. Sometimes, when trying to make Toad crash using a popup window, it does not always crash during the exit. Sometimes, it does so after re-opening the popup and navigating inside it.
I think it's a matter of the tree control (so, options LHS, describe window's list of sub-procs, help-about license display, the main area of Oracle Homes dialog) having focus when the window closes.
Judging from your call stacks, the access violation seems to be that the windows narrator is trying to read something from our controls while the window is closing. So we're trying to access something that suddenly disappears, hence the error.
ESC and the top-right X activate the exact same code, as far as I'm aware. The only difference might be that clicking the Close button (as opposed to hitting ESC) moves the focus away from the tree. So maybe if you click close (as opposed to X or ESC) after clicking in the tree, you won't get the error.
This is so puzzling. I keep rechecking the Narrator in settings, and it is always off.
