Bugzilla – Full Text Bug Listing
| Summary: | Implement Drop to Frame command handler | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] TCF | Reporter: | Anton Leherbauer <aleherb+eclipse> | ||||
| Component: | Debug | Assignee: | Project Inbox <tcf.debug-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | eugene | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 0.4.0 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
I have changed TCFActionStepOut to support drop to frame without repeating the action, and added canCount() call, so it will use step counts when supported by the agent. It allows to remove Repeat class in "Drop to frame" command handler that simplifies the logic and eliminates unwanted UI updates during the command execution. I have modified the patch to use the new functionality of TCFActionStepOut. Committed. Thanks! Very elegant, thank you! |
Created attachment 186824 [details] Drop to frame command Attached patch adds a "Drop to frame" command handler. The handler is enabled only for stack frames below the top frame. The command performs as many step out operations as necessary to reach the selected stack frame. I tried to implement this using a step count > 1, but this resulted in an error from the agent.