• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    is SET POINT VALUE display is possible to modify ?

    Mango General
    2
    2
    1.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      JF89
      last edited by

      Hello,

      Is it possible to change the font size of SET POINT VALUE objects?, and the size of vertical arrows ?

      0_1565973130087_Courbe chauffage.png

      The text associated with the SET POINT VALUE variable is not displayed. (when page running)

      0_1565973172401_Courbe chauffage_maxi.png

      Is it a problem of setting?

      Best regards

      1 Reply Last reply Reply Quote 0
      • phildunlapP
        phildunlap
        last edited by

        Hi JF89,

        You could change the font size with a little CSS. One could do it globally on the /ui/administration/ui-settings page by setting the User stylesheet URL to point to a CSS file with something like

        md-input-container {
            font-size: 20px;
        }
        

        But you may see negative side effects depending on size and whatnot.

        The text associated with the SET POINT VALUE variable is not displayed. (when page running)

        There are HTML attributes which the components can't actually accept. The Dashboard Designer doesn't attempt to exhaust this validation because there are a lot of components and a lot of attributes! The live preview in the dashboard designer applies the text content as being the content of the element so it appears, but when the element is rendered on the actual page the component eliminates its errant contents.

        I would advise using another element for static text content.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post