Facility Control

 View Only
  • 1.  Avoid declaring hundreds of individual parameters for a system with a consistent structure

    Posted 10-11-2019 13:00

    Hello,

    I have a slight issue with the numbers of parameters I would like to implement. I have 4 brackets with 7 matches each in dashboard where you set the team by dropdown. Using an external XML data source, I then need to populate 5 parameters for each team, granting me the joys of declaring and maintaining 280 individual parameters of varying type until there's a change.

    I can think of a few alternative methods for a few of the parameters, but they involve me manually hardcoding the XML data into a script in Xpression and I need to use the external API as my source.

    Is there any way for me to only declare the parameters used for the dropdowns and then expose multiple variables to Xpression?

     

    Thanks



  • 2.  RE: Avoid declaring hundreds of individual parameters for a system with a consistent structure

    Posted 10-14-2019 08:46

    Not 100% sure I understand the question...
    There will definetly be alot of parameters when dealing with things like brackets etc like you're talking about...

    I dont know if it will help though but if the problem is handling the parameters in DashBoard, naming them in a usefull and descriptive/grouping way will make your life easier.
    Second, if it's the massive list in DataLinq (that you will get eventually) that is the problem, you can add a stream="false" to the parameter itself, and it will no longer stream to DataLinq. And yes, can only do this with code, there's no GUI checkbox or anything for it yet.

    See this post: https://support.rossvideo.com/hc/en-us/community/posts/360043588672-Parameter-Hide-from-DataLinq-Streaming


    #DashBoard


  • 3.  RE: Avoid declaring hundreds of individual parameters for a system with a consistent structure

    Posted 10-14-2019 08:59

    Hey,

    So my problem is that I would like to avoid declaring hundreds of params manually, even if I can do so by grouping them by name and menu directly in the .grid file. What if I need to add another parameter in the future etc?

    What I had hoped was possible was that I could do something like only passing the data through dashboard. For example:

    Declare local vars
    Read param for the selected team
    Parse data from XML with XPath and store the team data in local vars
    Export an new XML file that is read through datalinq, but generated through code

    Something like that would mean Dashboard would only need to have declared params for the actual team string arrays. But even if I would like to keep everything a param in the .grid there's no way for me to declare and maintain groups of params as far as I'm aware, similar to how you would declare a struct in most programming languages.

    My question is mostly an inquiry to make sure I'm not missing some obvious function.

     

    Thanks


    #DashBoard


  • 4.  RE: Avoid declaring hundreds of individual parameters for a system with a consistent structure

    Posted 10-14-2019 10:33

    Hmmm... Well, what you're talking about should be possible...

    • I know DashBoard can read from online sources...
    • I know DashBoard can use these to populate local parameters...
    • I know DashBoard can write external XML files...

    Making it all work together though, that's a different story alltogether...
    You can set up tables/structs for data groups in DashBoard, if that's what you're looking for, but having them auto add the parameters you need, or easilly add more parameters without some work, that's a different story...


    #DashBoard