• State Not Answered
  • Date
    velda - Former HES Forum Member
  • Date
  • Replies 12 replies
  • Subscribers 5 subscribers
  • Views 674 views
  • Users 0 members are here

faster access to the Fade Changes button?

perhaps its uncommon to use the button as much as i do every day, but il throw it out there anyway.

Its a bit of a pain keeping the Fade Changes button on the programmer window as i usually have it on an external monitor to free up space in the touchscreens for pallets. So in the heat of a show when im turning fade changes on or off its usually too slow to find the mouse, move it over, and hit the button on the external display. I end up moving the window to a touchscreen, hitting it, and then moving the window back.

It wouldnt be so bad if the cursor didnt move every time you touched the screens. Then i could just leave the cursor over the button most of the time.

It just seems like its such a useful feature that it deserves easier access for on the fly lighting which is usually pretty hectic anyway. That blank soft button on the top bar would be great.

There are some buttons on the hog that i dont think do a damn thing right now. Like the control button? Or have i just never looked into it? It would be great if some of those unused blank buttons could be mapped to Fade Changes or maybe even a macro in the settings somewhere.
Parents
  • 0
    Adam,

    One of our plans (as logged in enhancement #5868) is to add Fade Changes as one of the options for the customizable trackball buttons. This would give users a dedicated hard key for toggling the fade changes option in the current editor.

    You are correct that there are a couple of buttons on the console face panel that we are still in the process of implementing, but we try to be very careful when we do so to ensure that functionality we add is consistent with the concepts and syntax used for the rest of the console. Even if the Control key weren't already used, it wouldn't make much sense to use it for Fade Changes unless we were going to send out new key caps for it to all of our users.

    I'd like to follow up a bit on what Todd said. I generally only use my first 10 views, but one of the great features of the Wholehog 3 is that there are so many different ways that it can be setup and run. I just wanted to make sure that before you ran off and tried creating views with editors that you were aware that the Programmer is the only editor that can be recorded into views. You cannot record cue, scene, palette, or parked editors as a part of a view. The view will record, but any object-specific editors will not be recalled.

    Thanks.
Reply
  • 0
    Adam,

    One of our plans (as logged in enhancement #5868) is to add Fade Changes as one of the options for the customizable trackball buttons. This would give users a dedicated hard key for toggling the fade changes option in the current editor.

    You are correct that there are a couple of buttons on the console face panel that we are still in the process of implementing, but we try to be very careful when we do so to ensure that functionality we add is consistent with the concepts and syntax used for the rest of the console. Even if the Control key weren't already used, it wouldn't make much sense to use it for Fade Changes unless we were going to send out new key caps for it to all of our users.

    I'd like to follow up a bit on what Todd said. I generally only use my first 10 views, but one of the great features of the Wholehog 3 is that there are so many different ways that it can be setup and run. I just wanted to make sure that before you ran off and tried creating views with editors that you were aware that the Programmer is the only editor that can be recorded into views. You cannot record cue, scene, palette, or parked editors as a part of a view. The view will record, but any object-specific editors will not be recalled.

    Thanks.
Children
No Data
Related

www.etcconnect.com