• 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

    Possible bug in Public Views

    Development general discussion
    2
    3
    3.4k
    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.
    • V
      victor-br
      last edited by

      Hello,

      I´ve noticed sometimes the public views don´t render properly - background image and components don´t load, and all we get is the small "block" image in the place of each component (at least they are layed out at correct positions, but don´t actually "show" anything).

      This only happens at public views... everything works OK when normally loggin in and going to the graphical views.

      This is very random and unfortunately, difficult to reproduce. Reloading sometimes does the trick to fix it. One user reported it is related to the computer going to "sleep" or "hibernate" modes, and then coming back to operation, but I´ve personally seen Firefox with this same behavior, with no sleeping/hibernating involved.

      Has anyone had a similar experience? Any idea of how to debug this, or what technology could be causing this? (jsp, dwr/ajax...)?

      Thanks,

      best regards.

      1 Reply Last reply Reply Quote 0
      • M
        mlohbihler
        last edited by

        Hi Victor,

        What version are you seeing this in? I used to see this because the DataPointVO.lastValue property would be set with the latest value of the point, and view initialization depended upon it being different from the current value (because it only sends changes to the browser, and if there is no difference, no change is sent, and the point stays as a block). Personally though, i cannot now recreate the problem.

        A question though... The above condition should be cleared when the value of the point actually changes. Is this what you are seeing, or does the point always remain a block.

        Best regards,
        Matthew

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