Skip to main content
C
Christian_S1-Visitor
1-Visitor
June 28, 2019
Solved

Collection - image render bug

  • June 28, 2019
  • 1 reply
  • 3044 views

I have a CollectionWidget in an Mashup which shows things. Than I made Mashups for selected and unselected entries on which the thingname is passed. After the Loaded the GetAvatarURL() is called which puts the thing avatar to an image widget, therefore i now see the thing avatar on each collection entry.

 

But now when I change the selection sometimes the picture of another avatar is shown as avatar.

For example I have Machines "Square","Circle" and "Triangle".

 

Collection:

"Square"

"Square"

"Circle" --> Selected

"Square"

"Triangle"

 

When I now select the second entry which is a "Square" thing, the avatar of "Circle" is shown/rendered on this item.

 

listbug1.pnglistbug2.png

The difference between red and black square is just a css style for blackandwhite. But as you can see the Thingsymbol changed to the avatar of the squarething 😞

 

What should/can i do now to fix this behaviour? For me it seems like a rendering latency which is causing this problem.

 

 

Best answer by slangley

Hi @Christian_S.

 

Please be advised that this issue was addressed in the most recent releases of the product:  ThingWorx 8.5 and 8.4.6.

 

Regards.

 

--Sharon

1 reply

C
Christian_S1-VisitorAuthor
1-Visitor
July 2, 2019

It seems to be a problem caused by the "load/unload" feature. When I set it to "Load all" this problem seems to be solved.

 

Anyone has an idea?

S
slangleyCommunity Manager
Community Manager
July 2, 2019

Hi @Christian_S.

 

What version of ThingWorx are you running?  Is the behavior the same across browsers?

 

Regards.

 

--Sharon

C
Christian_S1-VisitorAuthor
1-Visitor
July 3, 2019

Currently we are working with ThingWorx 8.4.1-b2126

Same behaviour on Firefox, Chrome, IE.

 

It seems to me like something which could be caused by lazy async loading, on which data is requested for every entry and than given back async to a position which has been internaly changed due to load/unload feature and is than written to the wrong entry.

Terms & ConditionsCookie settingsAccessibility statement