Ask Your Question

Debug probe last evaluated code selection doesn't remain in history

asked 2022-04-25 08:23:30 -0600

martinako's avatar

updated 2022-05-02 10:19:21 -0600

I evaluate a section of code in the debug probe and it executes in the current context as expected. However, when I press up cursor to repeat the last executed block of code in the history it's not there anymore! so I have to make a selection of the code and evaluate again. Which breaks my focus as I have to repeat that same selection may times in a debug task.

For a test, I do the same for a smaller section of the same code. When I press the up cursor it's there. I start to increase the size of the code block and when it reaches 24 lines it stops remaining in the history.

Is there a setting anywhere that controls the maximum size of the executed code that goes in to the history? or is this a limitation? I started a new project in case the project files where corrupted but it didn't make any difference.

I'm using winpro

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2022-04-25 16:01:19 -0600

This is a limitation of Wing 7 and 8 (and earlier versions). We'll look at changing this in future releases.

edit flag offensive delete link more

answered 2022-05-02 10:22:39 -0600

You may be able to use the active ranges feature to solve this -- select the block of code in the editor, press the "set active range" icon in the Debug Probe (the icon with a stack of lines and a + sign) and then you can use the cog icon that appears to re-execute the active range at any time. Wing should do a reasonable job of tracking the boundaries of the range if you edit it.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2022-04-25 08:23:30 -0600

Seen: 122 times

Last updated: May 02 '22