We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
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.
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.