Thru

my vote is to keep the behavior the way it currently is. I would not be opposed to making it a desk setting, but can understand the reasons why the developers do not want to do that.

that's my two cents.

-Nate

Our current plan is to keep the thru behavior as it currently is.  In speaking with LDs, they very, very rarely use Active Flexi mode in live.  So, for them, the thru syntax is not a problem.  So, it becomes the programmers issue to understand the difference.  

I realize this is a hotly contested issue.  But, that is where we are falling in the decision.

Thanks much!

a

Our current plan is to keep the thru behavior as it currently is.  In speaking with LDs, they very, very rarely use Active Flexi mode in live.  So, for them, the thru syntax is not a problem.  So, it becomes the programmers issue to understand the difference.  

I realize this is a hotly contested issue.  But, that is where we are falling in the decision.

Thanks much!

a

Anne,

Since thru behavior will stay the same, can I still make my suggestion that the operator's flexi state be incorporated in the command line, i.e.:

• 1 thru active 10
• 1 thru patched 10
• 1 thru show 10

with the flexi state automatically posting with the press of [thru].

While I don't like to clutter up the command line, I think this would do two things:

• serve as a reminder to the operator as to which flexi state they are in, especially if they have more than one live tab open
• allow the designer to see the operator's flexi state

Thoughts?

-Todd