I don’t really think it is a bug. I’m using that word loosely here. It doesn’t really fit the definition of something I would consider important to take action on. Your logic seems to make sense, however:
- There might be some reason I haven’t considered that our designers chose to put it there.
- Since there are many folks who use the CUDA toolkit and haven’t mentioned this issue, there may be considerable expectations in the development community about where to find it. Making UI changes like that is not something I have expertise in so wouldn’t make a judgement.
- This strikes me as a very low priority issue.
It’s OK if you disagree with me. You have the bug filing portal at your disposal to address your concerns. This is a community and its the nature of community to occasionally disagree.
Where I can determine that something is obviously broken, and/or is potentially a serious issue (which claim I wouldn’t make here) then I very often do file bugs, whether a customer chooses to or not.
There are other good reasons for you to file a bug.
- If you file a bug, your opinion expressed that way carries additional weight in our system. The people who handle bug triage very often ask for more information, and communicate back and forth with the person who filed the bug.
- If you file a bug, you get automated information about the progress of the bug. If I file it, you don’t.
I assure you I take pride in our products, and file many bugs.
FWIW, I filed a bug for you. 2733262
I won’t be able to respond to requests for information about the progress of that bug. That is not a scalable process for me (nor is intended by NVIDIA to be how we scale that process); the mechanism that NVIDIA has provided for that sort of information is for you to file a bug.