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.
What do you think about : Debug -> Run to Cursor (forces start of debugger, if class has main() or is JUnit test) -> New Watch -> Break point -> line -> Break point -> type -> class -> exception -> method -> thread -> field -> Edit Value -> Copy Value (first approach to sophisticated DnD) -> Paste Value ( " " " " ) -> Display Tooltip As -> object id (#123) -> decimal (if array, display as: 1, 22, 3, 74456, ...) -> hex (if on String, display as: 3F 71 FF ...) -> octal -> binary -> char -> array content (Example: 3F 71 FF ...) -> string (useful on array of byte, char, int) (if on object, display toString()) -> Display All Tooltips As -> decimal (bounded on respective variable type) -> ...
-> Display All Tooltips As -> ... -> remember current settings for next debugger session -> default
*** Issue 155107 has been marked as a duplicate of this issue. ***
IMHO shouldn't Issue 155107 better linked by 'depends on' than marking it as duplicate?
Erroneously values had been changed by cross-posting :-(
Debug -> Show history Id would be great If I could see how in time variables/class atributes are changing. For examples in threaded loops.