Facility Control

 View Only
  • 1.  Moving existing buttons to a tab layout

    Posted 04-27-2019 23:12

    I'm relatively new to Dashboard and have managed to create a number of buttons to run various custom controls among other things.

    Now I'd like to organize my work into tabs so I created a tabbed canvas object next to the buttons but when I try to drag/drop a button onto a tab, it disappears behind the tab canvas.  I can bring it to the front but it's not within the tab itself, just on top of it and moving the tab canvas leaves the button behind.

    What am I doing wrong?  I can certainly create new buttons on each tab but there must be a way to place existing buttons onto a tab that I'm not seeing.

    Somewhat related: I dragged the IP address of the frame to the canvas as my starting point but I don't want it to be shown, just the buttons should be visible.  So far, the only way I know how to hide it is to place a button over top.  Is there a better way?

    Thanks,

    Curtis



  • 2.  RE: Moving existing buttons to a tab layout

    Posted 04-28-2019 22:07

    Hi there! And welcome to DashBoard!

    As an answer to your question, yes there is!

    Every element in DashBoard, be this a button, a text field, a scroll, a fader or a canvas or a tab, they all allign on a layer, and the last thing you created will be on the top layer (unless you right click it and tell it to move down.

    Now if you drag and drop something you'll see that you can overlap things and see how they cover eachother up etc.

    In your example, if you first select your button, and then move it to the top layer, and move it over the tab, it will show, but it wont hide again if you choose another tab, and it will not follow the tab if you move the tab.
    However if you create a button INSIDE the tab now, you'll notice that it appears and hides as you would expect, and that if you move the tab, the button moves with it.

    But! No, you dont have to recreate all your buttons etc. Organizing is good!

    So, what you do, is mark your button you want to move, then CUT (ctrl+x), then SELECT the background of your tab, and PASTE (ctrl+v), this will put the button in the top left corner of THAT tab, and inside THAT canvas, so it behaves as you expect it to. Now if you take your second element/button, cut that out, and select the button that you placed inside the tab allready, and then paste, you'll notice that it placed it in the top left corner of that element. And there you go!


    #DashBoard


  • 3.  RE: Moving existing buttons to a tab layout

    Posted 04-29-2019 14:54

    Hi Aleksander,

    So simple and yet I completely overlooked the obvious method of cut/paste :-)

    What I managed to do though in the meantime was to go to the Source tab and copy/paste the code for each object that I wanted to move to a tab.  Sort of the same thing I guess, except a little more work than your suggestion which I like much better.

    Thanks for your help!

    Curtis


    #DashBoard


  • 4.  RE: Moving existing buttons to a tab layout

    Posted 04-29-2019 15:15

    What you did was basically just the same.
    Just a bit harder to grasp for many people.

    But happy to help!


    #DashBoard


  • 5.  RE: Moving existing buttons to a tab layout

    Posted 04-29-2019 15:41

    By the way, do you have any advice on my related question above (hiding the IP address of the frame) ?

    i.e. is there a "visibility" option for an object or do you just cover it up with another object like I have done?

    Thanks


    #DashBoard


  • 6.  RE: Moving existing buttons to a tab layout

    Posted 04-29-2019 22:28

    Yeah that can be done, it can basically be done with any element in DashBoard.

    1. Give your element (input, text, canvas, etc) an ID so that we can access it.
    2. Find the element in question, and give it the attribute visible="false" - this will make sure it's hidden when the DashBoard loads up.
    3. If you want to show said element again, in any task/button you can add the "reveal" task
      (found under Control and APIs -> ogScript -> Panel Elements -> Reveal).
    4. In the drop-down of the "reveal" you'll find the ID of the element again, assign it, and that's it.

    Then again, if you dont want the parameter input to be shown at all, there's no reason to have it in the DashBoard at all. The parameter will still be stored in the DashBoard (accessible under the "Parameters" button next to bottom in the Edit Mode tools.
    Or you can change the text input from a text field to read-only if you uncheck the checkbox next to "widget hint" saying "Get value from parameter". Then you can swap the type of widget you want to show. Read-only will let you see, but not change the IP value.


    #DashBoard


  • 7.  RE: Moving existing buttons to a tab layout

    Posted 06-18-2019 01:05

    Thanks very much!  Apologies for the delay, I got distracted onto another project :-)


    #DashBoard


  • 8.  RE: Moving existing buttons to a tab layout

    Posted 06-22-2019 12:39

    Thank you Aleksander, I had the same question re moving buttons between tab layouts and you steered me on the right path. Thanks again

     

    Whit


    #DashBoard