Having the smallest change in position force the re-download of a potentially many MB file would be far worse for most use cases of editing. However, I agree that forcing a given resource URL out of the cache would be a nice bit of functionality to expose to scripts. There is already an existing function
refresh(QUrl url) on the resource cache class, from which ModelCache is derived, and ModelCache is exposed to scripts. Unfortunately the function isn’t marked as being invokable from scripts, so there’s no way to call it.
It should be possible to modify the
refresh method to be callable from scripts, which would allow people to either write a script that opens a query dialog and lets you paste a model URL to be refreshed, or to modify the edit script to add a button that does the same.
I think that this will trigger a re-download if the server reports the content as changed, but I’m not 100% certain.
I’ve created a PR here so you can try it out by manually executing a refresh in a console window or custom script and see if it does what you want. If so, we can look at integrating UI into the entity properties window to add reload buttons by model URLs to make it easier to force a reload.