Bug #17238 2010-06-11 00:47
codywilson
Global Variable Editor does not accept no for an answer
When trying to open a project that uses an undefined global variable, the Global Variable Editor appears and asks the user to define the variable. If the user does not or cannot define the variable at the the time and tries to presses the "Close" button the Global Variable Editor reopens and the notice is repeated, making Codes::Blocks effectively unresponsive. While this can easily be remedied by typing something for the value, it is somewhat annoying and entering invalid variable values could cause problems.
- Category
- Application::WrongBehaviour
- Group
- Status
- Open
- Close date
- Assigned to
- jenslody
History
Code::Blocks asks for any occurrence of the undefined variable.
We can try to remember that we have asked for the variable and do not ask again.
But that can lead to problems, too, because the user might forget to define the variable (if really needed) and that will most likely lead to compile-/link-time errors.
If I remember right, there was already a discussion in the forum about that issue, but I can not find it at the moment.