Adaptable Subroutine setting

[Intaris]

Life can be a real beach when working on a load of high-performance VIs which have a bug somewhere.  First spend half an hour un-setting "Subroutine" on a tree of VIs, then find the bug, spend another half an hour re-enabling sub-routine execution and then spend a further half an hour finding the last subVI you forgot because you've noticed a problem when benchmarking......

How about setting a VI to conditional subrouting meaning that it retains its subroutine status until you place a probe or breakpoint in it  (It would be nice if calling VIs adapted also of course).  As soon as the breakpoint / probe are removed, return as normal to subroutine execution.  Man would this save a lot of time.

Shane.

[altenbach]

This goes along the lines of quickly enabling/disabling debugging, which has already been suggested. Maybe this should apply to all VIs. If you place a probe on a diagram with debugging disabled, temporary debugging should be enabled automatically. Of course debugging requires a recompile, so placing a probe when the VI is already running will not work.

Does changing to/from subroutine priority require a recompile?

(I wonder why you use subroutine priorities at all, there could be penalties under certain conditions. Have you tried inlining?)

[Intaris]

Ah, I had searched but didn't find anytthing.

I suppose it's a pretty close match to the other idea, even though mine is kind of focussing on the subroutine priority which is really important for us on RT.

We're on LV 8.5 so I can't comment on inlining yet.  We can't inline LVOOP code though, but we can make it subroutine priority....