There is a tiny bug in the Customize Toolbar dialog. In the Commands tab, on clicking the last command in the commands list of a category, the list jumps up to reveal the next two commands on the list, but the one that gets selected is the one BELOW the one that was clicked.
For example, when I first go into the File category, Navigate Forward is the last command in the list. If I click Navigate Forward, the commands list jumps to expose New PL/SQL Object and SQL Recall, but the one that is select (focused/highlighted) is New PL/SQL Object, which is just below the one that was clicked, Navigate Forward.
Another bug that is not QUITE as tiny is that the Description at the bottom never populates. I tried resizing the window, but Description remains a small empty zone at the bottom. If I resize the window past the last command in the commands list, the boxes above Description just "blank fill" and Description does not expand. I don't know if there is supposed to be Descriptions of the selections or not. I tried many of them, but none of them populated Description. Now, it may be that Description requires Internet access, but we do not have that in our client's VDI. We can use nothing in the VDI that requires Internet access.
Finally, it would be nice if there was a "separator" object for custom toolbars to help group toolbar buttons. As it is, we have to have multiple custom toolbars, but in dark mode, that is very hard to see anyway. A bright separator would be better. What I was trying to do was to create a custom toolbar with the buttons I most often use.
I can't reproduce your File category, Navigate Forward example. Not sure yet what's going on there.
Description, is just not used. We could add a description to each of the items in the menu. If we did, it would show up there. But we haven't added any descriptions.
Finally one I can be helpful on. First, put all of the items you want into a single custom toolbar. Then, while the "customize" dialog is still open, right-click on a toolbar item that you want to put a separator before, and click "Begin Group". You also have some options there for text on the new buttons if you want that.
OK I see that. The group separator is very faint in this Cobalt theme. I may try other themes to see how it looks, but of course, Toad has to restart with each change.
For the command list scrolling selection issue, it is affected by the size of the window. If the last item in the list is fully in view, it is just selected without the list scrolling. To go to the next, I have to scroll the window or hit down arrow. If the last item is not fully in view, that is when the problem arises and then only when I click the last item. Down arrow does scroll the list, but the selected item is the next one down instead of two down. The size of the window is probably affected by my Windows "Make Everything Bigger" setting:
That is probably causing the little Customize window to be just the right size that the last visible entry is not completely visible. Then, I click and it jumps and selects the wrong one. I tried various expansions of the window and found that when the last item is fully in view, it is selected and the list does not scroll. Other sizes produced the anomalous behavior.
Description is not terribly important. There is the F1-Help, which is pretty good. It is just confusing to have Description and not describe anything. If I were you, I would just get rid of Description in that window. Everyone ought to know that they can hit F1 and go right to the page's help entry.
We talked a while back about an online documentation resource. Have you folks discussed doing that--maybe a wiki or something? While we cannot get to the Internet inside the VDI, we still have access to I-net outside in the host, so a wiki or similar resource would be great.
I would not call it the culprit. It is clearly changing the geometry of the window, but it is not causing the invalid selection result. Something in Toad is selecting the wrong one after the scroll. Now, it may be that Toad is selecting the one that it "thinks" is at the bottom instead of the one that was actually clicked.
There's no plan for online documentation at this time. It is a great idea, but we do not have a dedicated documentation resource to tackle a project of this scale.
