Feature request: being able to use the debug button when the vba code is protected from viewing

Problem: When a user encounters an error and the vba project is protected from viewing, currently the debug button is disabled and the user can only press "End" to stop the code. As a developer, this makes it cumbersome to troubleshoot - it's not always easy to reproduce the bug, which currently involves ending the code, unlocking the project, and then restarting the code hoping that the same error will occur again.

Solution: Always allow the debug button to be pressed, even if the project is locked from viewing - but if the project is locked from viewing, prompt the user for the vba password to unlock the code.

That would allow me to troubleshoot right at the moment the error occurs, rather than going through the hassle of attempting to reproduce it.