# History breakpoint suggestions

**URL:** <https://discourse.shapr3d.com/t/history-breakpoint-suggestions/30804>\
**Category:** Feature requests\
**Created:** [March 15, 2024, 8:43pm UTC](https://discourse.shapr3d.com/t/history-breakpoint-suggestions/30804 "2024-03-15T20:43:40Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![justin](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@justin](https://discourse.shapr3d.com/u/justin)\
**Post date:** [March 15, 2024, 8:43pm UTC](https://discourse.shapr3d.com/t/history-breakpoint-suggestions/30804/1 "2024-03-15T20:43:40Z")

</div>

1. This is _super_ minor, and might just be my workflow, but basically every time I’ve set a breakpoint, it’s been with the intention of rolling the history back to _before_ a specific event, so it feels strange to have to select the item before the one I’m trying to turn off, since Insert Breakpoint does so _after_ the selected action. Having the option to “Insert Breakpoint Before” or “Insert Breakpoint After” wouldn’t change the number of required clicks, and would clarify what’s happening for newer users.

2. Being able to disable breakpoints without deleting them would be useful in my workflow. For example, I have a project with rotational symmetry of some of the parts. In my history is a move action that copies and rotates those parts. Fairly often when working on the symmetrical parts, I’ll add a breakpoint before the move action. Being able to keep that breakpoint there, just disabled, would make that action easier to find and speed up my workflow.

3. Along the same lines, if breakpoints could be kept and toggled, being able to rename them would be useful.

---

<div class="post-metadata">

**Author:** ![Steve](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/steve/32/2446_2.png) [@Steve](https://discourse.shapr3d.com/u/Steve)\
**Post date:** [March 16, 2024, 12:40am UTC](https://discourse.shapr3d.com/t/history-breakpoint-suggestions/30804/2 "2024-03-16T00:40:05Z")

</div>

Along similar lines, adding a single step feature after breakpoints (like a computer program debugger) would be great. I’m impressed with the parametric feature and can see a lot of potential, but I have a lot to learn to take full advantage.

The breakpoints, and the highlighted parts matching the selected step are helpful, but I find it hard to determine exactly what is happening when — especially when no breakpoint is active and I’m just randomly selecting steps in the history list. The ability to easily go “one step at a time” (again, like a debugger) would help a lot, and avoid having to set a lot of extra breakpoints just to hide all of the “after” steps.

---

<div class="post-metadata">

**Author:** ![Xdrakosha](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/xdrakosha/32/24881_2.png) [@Xdrakosha](https://discourse.shapr3d.com/u/Xdrakosha)\
**Post date:** [March 16, 2024, 6:40am UTC](https://discourse.shapr3d.com/t/history-breakpoint-suggestions/30804/3 "2024-03-16T06:40:25Z")

</div>

You can drag breakpoint down one by one.

---

<div class="post-metadata">

**Author:** ![Steve](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/steve/32/2446_2.png) [@Steve](https://discourse.shapr3d.com/u/Steve)\
**Post date:** [March 16, 2024, 11:51pm UTC](https://discourse.shapr3d.com/t/history-breakpoint-suggestions/30804/4 "2024-03-16T23:51:27Z")

</div>

Thanks, didn’t realize that. Still, a single step button would be a little easier to use.

---

<div class="post-metadata">

**Author:** ![dloveaus](https://avatars.discourse-cdn.com/v4/letter/d/41988e/32.png) [@dloveaus](https://discourse.shapr3d.com/u/dloveaus)\
**Post date:** [March 18, 2024, 9:19am UTC](https://discourse.shapr3d.com/t/history-breakpoint-suggestions/30804/5 "2024-03-18T09:19:41Z")

</div>

Made the same suggestions last month. Yes, I support this:

> [@Reusable Breakpoints](https://discourse.shapr3d.com/t/reusable-breakpoints/30279):
>
> Please follow the format below for requesting a feature. The problem that this feature will solve: Especially when using duplicated parts, I model the part in a few operations and then use copy or pattern to make the duplicates I need. Then, if I need to modify the duplicated components, I find the copy or pattern function in history and set a breakpoint just before it, do the modifications and then delete the breakpoint. Being able to name breakpoints and leave them inactive in history wou…