I have noticed that my uibuilder webpage sometimes takes a really long time to refresh. Usually it refreshes within a second, but it then reverts to 10+ seconds after some time in use.
In the network tab of the console I can see a websocket that keeps increasing in time. It may have nothing to do with the lag, but I don't really understand the back-end at all, so thought it might indicate the nature of the issue...
I think that you will need to turn on debug for the front-end. Which version of uibuilder are you using?
I think you are using the non-minimised version of the front-end library? This will be slightly slower than the minimised version but isn't the cause of what you are seeing there.
There is something very odd about that network chart. Why are the same resources being loaded multiple times? Also, I'm not sure what the "Initiator" column is showing things like websocket.js since that isn't used (at least directly) by Socket.IO which is what uibuilder uses.
The interesting thing is that it still hasn't happened today, so I am starting to think that it was something to do with my code at the time.
I'm not loading any new libraries since a very long time ago, so that can't be the cause.
I have loaded components (of course), as that's the fun of using Parcel to compile
I'll keep an eagle eye on it, perhaps it will never come back again.
It tell you one thing, I bit off quite a bit getting audio fully functional in the floorplan. I still have some way to go before it's "production" ready...
On the face of it, it looks like its working, but there is quite some back-end work I want to do to make it "child" proof
FYI, I'm going to rebuild the playlist shortcuts to probably use drop downs, so I can include more of my collection .... you can see since I've had kids, that I appreciate "chilling" a lot more these days... haha!
I have found out what the issue most likely was. I had a 2nd web page open on another PC whilst I was developing on my main PC and I came across an inexplicable bug.. Spent hours debugging it with the help of @unborn, in the end I want to say that it clicked that I should refresh the “other” web page, but in reality I was at a loss for what else to do… I’d tried everything you can imagine from restarting flows, restarting node-red, rebooting the pc, clearing the browser cache, trawling through my code over and over again, commenting parts out, you get the idea. In the end, lesson learnt.
it will never come back again.
