Thru Thru

So just finsihed programming my 1st show on 1.7.  Why did you people make the thru syntax different????  I don't understand.  I understand how it works now, but WHY?  I run 3 screens, 1 active, 1 patched channels, and a playback.   So I run active so I can see whats active in the cue.  Its a real bummer to make sure my patched screen is highlighted before i type 1 thru 20 @ 50.  If i'm on the active screen and those channels are not active they will not be selected unless i type thru thru.  I thought we already had this before.   Before if I was in Active and i wanted only the channels that are active I would type 1 thru 20 select active.  Simple, no problem everything works great.  It really sucks to type thru thru, or look up to see which screen is highlighted, switch to the patched screen.  I just don't get why you guys ruined THRU!!!!!!  Maybe it's just me but I find this a real pain.  Since when I goto blind running an Active and patched views I have to do the same thing.   Sorry about the raint!

 But I would love to see thru go back the way it should be!!!

I would love to hear other programmers view on this.

Thanks

Parents
  • I mostly work in the active channels flexi-state. I have to agree that I do not care for the way thru and thru thru work.  Thru should grab all channels in the range whether they are active or not. Thru Thru should be Thru + Select Active or like the Thru On button on the Strand 550 series. Just my oinion...

    Bunny

     

Reply
  • I mostly work in the active channels flexi-state. I have to agree that I do not care for the way thru and thru thru work.  Thru should grab all channels in the range whether they are active or not. Thru Thru should be Thru + Select Active or like the Thru On button on the Strand 550 series. Just my oinion...

    Bunny

     

Children
No Data
Related