v8.3.0
When using the Configuration Explorer (CE) to find and edit View component bindings, I noticed that if I double click in the CE on a binding to edit it and OK the changes, then open it back up again from the CE, the binding editor shows the original binding. However if I find the prop in the Project Browser and open the binding from there, it’s correctly applied the new binding. It looks like the CE is caching the values and opening the binding editor up with the cached value instead of the live.
You need to click "Refresh" in the top right corner. It doesn't auto-refresh the UI.
1 Like
Yeah, I couldn't tell you exactly why it works that way (been a long time since I made the configuration explorer, and I'm mostly just happy anyone uses it) but the config explorer does exactly what you suspect - it basically holds on to what the config is at the moment it walked through your view, and when you hit 'Go To Reference' it brings up that cached config instead of the 'live' config in the binding.
A quick glance at the code suggests that it would be surprisingly harder to refactor than you might think, but it's still worth a ticket I think.
1 Like
It’s pretty handy! We use it all the time, the filtering is what really gives it value, I guess i’ve just never made a mistake and had to re-open the binding to fix it from there…. 
that’s the sales pitch for me anyway
1 Like