Community
Participate
Working Groups
I was debugging code like: if (action == null) { action= (IAction) fActions.remove(actionID); if (action != null) fActivationCodeTrigger.unregisterActionFromKeyActivation(action); } else { fActions.put(actionID, action); fActivationCodeTrigger.registerActionForKeyActivation(action); } and I was on code before this if/esle block. I set the cursor on the remove call for when the action is null and said Step into Selection. The action was not null so I never hit the step into selection. I continued debugger and then magically suspended claiming I had hit a run to line breakpoint.
This is the same limitation that Run To Line has (in fact, it's the same code). We should add this to the ReadMe.
I don't know where the readme file is. :-) Any help, DarinW?
The read-me file is owned by Jim des Rivieres. Jim, does the 3.0 release readme file exist in a plug-in somewhere?
The 3.0 release note document have not been started yet. Please write the release note text, paste it into this problem report, and tag the report with keyword "readme".
Add to 3.0 readme notes.
I believe this is just a dup of bug 36914. If the program suspends before the step into selection, it should be cancelled. If the program does not suspend before the step into selection (but arrives much later) - then so be it.
*** This bug has been marked as a duplicate of 36914 ***