Breakpoint weirdness

[TheThirdOne]

I found two issues with breakpoints while playing around with timertool for #80.

1. Changing a breakpoint does not have an affect on a running program until it is paused and then restarted. Breakpoints are passed to the simulator thread as function arguments (which is definitely necessary), but that means changes to the UI do not affect the simulator until the threads is shut down and restarted. A solution to this would be to pause and rerun if a breakpoint is changed mid-simulation.
2. Assembling, marking a breakpoint and reassembling results in a visual breakpoint, but is removed when the program starts running or switch away from assembled view. I am not quite sure as to the cause of this.

These issues aren't a priority as each has simple workarounds. They should be pretty easy to solve though.

[Sivachow]

So does this mean, the break points should not be removed when re assembled ? And I did not understand the part where, switch away from assembled view means as well. Thank you

[TheThirdOne]

So does this mean, the break points should not be removed when re assembled ?

The bug is that there is a breakpoint visually, but it does not actually function. I don't particularly care whether the breakpoint "should" be there or not.

And I did not understand the part where, switch away from assembled view means as well. Thank you

By "switch away from assembled view", I mean going from the "Execute" tab to the "Edit" tab.