Home AMX User Forum NetLinx Studio

MVP navigation keys

I'm quite new in this. I wonder how most people program this navigation keys on 8400i and 5200i. What do u use it for? Can I see some sample codes you guys used?

Comments

  • jjamesjjames Posts: 2,908
    External Hard Buttons

    I assume you're talking about the external hard buttons on both the MVP-8400 & MVP-5200.

    On the 8400s, we use the directional pad for just that: directional input of the controlled device. The four buttons on the left hand side we use for volume up / down and channel up / down. It makes it easy to turn the volume up and down without having to look at the panel.

    On the 5200, we were saddened that they took away the four extra buttons. However, they did add a rotating wheel, so now we're just missing two (essentially.) We use the rotating wheel for volume (clockwise is volume up & counterclockwise is volume down.) Since we lost two buttons, we add channel up and channel down near the corner of the screen so one could feel the edge & corner and know about where the channel buttons are, again not requiring you to look at the panel to channel up and down.

    There's not any code I can show you because it's all dependent on what you need them to do. So if they were volume buttons (for the 8400), it'd be a simple BUTTON_EVENT[dvTP, nVOLUME_BTNS] and then it'd run the specified code for volume.
  • I always add the channel codes in TPDesign.

    When you view a page press Ctrl+B to show external controls or open the external controls page at the top of the TP files tree.

    The external controls page is where global channel and address codes go.

    If you want to set different codes for specific pages then you need to press Ctrl+B while viewing it, select the button whose code you want to change, set 'Overide Global' to yes on the general tab in the properties and then add your channel or address code.

    I'm sure you can do this from code but this method works just fine.
  • DHawthorneDHawthorne Posts: 4,584
    I used to always do it in code ... for some reason or another, I wasn't aware of the "Override Global" setting until I had a lot of projects under my belt. The way I did it was put a SWITCH...CASE in the button event for them, and then send commands depending on the context or source active. Mostly I use them for the nav cluster on devices that use them so I can utilize actual screen real estate better.
Sign In or Register to comment.