I am running your desklet on Linux Mint 21 (Cinnamon Version 5.4.12).
I noticed when I use a VPN (Torguard) at system startup, the delay in setting up the VPN causes the initial GET requests to fail. This leaves a desklet displaying, "Loading coin data..". So was assuming once that polling timer elapses another GET request will go out. I set the refresh timer to the minimum of 5 minutes.
What I noticed was that on that when logged into the coinmarketcap API page, that the subsequent requests are seen (every 5 minutes) and they are deemed successful.
But the desklet itself does not display the data. In order to display the data, I need to configure the disklet, cut the API key, so the "Missing API" message shows up, then paste it back in at which point the desklet works normally.
Obviously the initial request failing is not an app issue. But it is strange the subsequent requests fail as well.
So I repeated the whole test, by disabling my NIC and wireless (so no VPN this time). Once loaded into the environment (desklets have failed as expected). In this case, the same thing happened. Sorry I was testing this as I typed the above, so I guess the VPN bit doesn't apply.
It appears if the initial request is not serviced, the subsequent requests even though registered at the far end, do not induce the correct content to display.
Hi,
I am running your desklet on Linux Mint 21 (Cinnamon Version 5.4.12).
I noticed when I use a VPN (Torguard) at system startup, the delay in setting up the VPN causes the initial GET requests to fail. This leaves a desklet displaying, "Loading coin data..". So was assuming once that polling timer elapses another GET request will go out. I set the refresh timer to the minimum of 5 minutes.
What I noticed was that on that when logged into the coinmarketcap API page, that the subsequent requests are seen (every 5 minutes) and they are deemed successful.
But the desklet itself does not display the data. In order to display the data, I need to configure the disklet, cut the API key, so the "Missing API" message shows up, then paste it back in at which point the desklet works normally.
Obviously the initial request failing is not an app issue. But it is strange the subsequent requests fail as well.
So I repeated the whole test, by disabling my NIC and wireless (so no VPN this time). Once loaded into the environment (desklets have failed as expected). In this case, the same thing happened. Sorry I was testing this as I typed the above, so I guess the VPN bit doesn't apply.
It appears if the initial request is not serviced, the subsequent requests even though registered at the far end, do not induce the correct content to display.
Thanks