Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

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

V

Topics created by victor-br

V

Possible bug in Public Views

Development general discussion
• • • victor-br

3

0
Votes

3
Posts

3.0k
Views

M

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.