This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
NB 20091111 Run IDE with a fresh userdir and open some issue with a stacktrace (open some Kenai project and find an issue, for example). Click any line of the stacktrace -> nothing happens. In this situation, user should get some feedback about what happens and why the action he/she performed didn't have the result he/she expected.
cc xdesign
Generally agreed. Tomas, can we do (with reasonable time investment) the "link highlighting" at runtime, only when we find out that the link actually "leads somewhere"? If not, probably a dialog box notifying the user that the link target location can not be found would do the trick.
> Generally agreed. Tomas, can we do (with reasonable time investment) the "link highlighting" at runtime, only when we find out that the link actually "leads somewhere"? - some lines in the stacktrace might be valid, another not - So we had to check every line - could take some time... - the project could be opened in the meantime - we had to check and rerender every stacktrace. - it's not only about projects ... a change in a java platform settings (sources added, removed) should be also refrlected in the stactarces > If not, probably a dialog box notifying the user that the link target location can not be found would do the trick. yes. sounds as a quite simpler but still a solid solution. A dialog with an error msg + open project button. What do you think?
... sounds OK to me...