It seems inconsistent that when the build is “paused” (eg, hits a breakpoint), you can’t double-click on an action to modify it, but you can use the Action Inspector. Could double-click be enabled in this case?
Steve
That’s actually a bug, you shouldn’t be able to modify an action at all while the build is running.
Really? Why not? It’s so useful to be able to do that, if by “running” you include “paused”.
Steve
It was an original design decision way back in the FB1 days (Vincent will have to confirm this, but that’s my understanding anyway).
There are some actions and also some properties that could cause problems if the action properties were modified during a run. For example the iterators and loops, as well as properties like enabled, fail on error, etc.
Modifying variables during a run, on the other hand, is fine… and can be done in the watches panel.
Hmm, would it be possible to just warn the user that it may be A Bad Idea ™? Again, thinking of VB, it generally lets you modify your code at runtime, but occasionally says your change will require the project to be restarted.
I guess I still don’t understand the FB “runtime” model. There is clearly a difference between executing steps individually (ctrl+alt+F5), and stepping over them as a sequence (with F10), but I don’t quite grok it yet.
Steve
Yeah, it’s something we probably should revisit to see if it can be enabled. We’ll discuss it at our next team meeting.