Am I the only one, or does someone else think it would be handy for the C51 tools to open the source file and locate for where a reference is made to an unresolved external? I just deleted a routine that I know I don't want, but there was some scattered test code that referenced it. I get a stack of L2 warnings, but when I click on them, the tools doesn't do anything. It would be great if it went to the location of the warning.
L2 is a linker warning. The linker does not reference the C source file (since the source may not be available). If you don't get a C compiler warning, then the function is probably prototyped somewhere. Remove the prototype and the C compiler will warn you of acccess to an unprototyped function. Jon
Unfortunately, even the help for 'C' compiler errors doesn't work properly :-( You're supposed to be able to just click on the error/warning, press F1 and presto! the help for that particular message should appear. But mostly, it just brings up the C51 Library reference instead! :-( The only workaround I've found is to ensure that a non-source editor window has the focus before you click the message & press F1!
You're supposed to be able to just click on the error/warning, press F1 and presto! the help for that particular message should appear. But mostly, it just brings up the C51 Library reference instead! Is that with a single-click or a double-click? I've never had uVision2 fail to bring up the error message. If you single-click on the error message, this brings the focus to the output window. If you double-click on the error message, this brings focus to the editor window for the source file and line where the error occurred. I think there are some double-clicker utilities (or maybe it's a feature of windows) that automatically double-click for you. You'll have to turn this off to get single-click back again. Jon
Is that with a single-click or a double-click? I've never had uVision2 fail to bring up the error message. Single-click the message, then press F1. I've never had it bring up the right help unless I make sure that a non-source editor window has the focus before the click! That's with the Eval & dongled versions; on Win98 and NT4. I think Win2k is the same, but won't be able to try it til next year now! I'm sure I've mentioned it here before, and to support.intl The double-click to find the source line works fine, where appropriate.