I am always putting flat sequence structures around "set" and "unset" busy cursors because if I wire error clusters into them to enforce data flow and an error is passed in, they don't execute. Nothing like having an error occur then your cursor stuck as busy. I suggest having these two subVIs execute even if an error is passed in (just like reference closing/releasing functions do). This way the error cluster can be used to enforce data flow and we can all avoid unnecessary flat sequences. The only issue I see with changing this is if previous code has been written taking the current functionality into account and expects a cursor to stay busy when an error happens and unset busy is managed in the error handling state, or something of the like.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.