Dataview view containers change size on auto-reload

[fcskit]

What happened?

I use custom dataview view containers a lot in my notes to create renderings of my notes metadata. I like to have the auto-reload option activated so that changes of the metadata will be updated in the view. However, there is a catch. Dataview's auto-reload option updates the views in a fixed time interval even if the metadata has not changed. Performance wise this is not a big issue but the view containers change size while the content is updated. This causes the view of the current note to jump around, which is annoying when you edit the note.

Suggested fix
Do not updated the dataview view containers on every reload but only if the metadata of the file has been changed. I don't know if this is somehow directly supported by the obsidian api, but if not, although a little dirty, a deep comparison of the old and new metadata should probably do the trick.

DQL

No response

JS

No response

Dataview Version

0.5.67

Obsidian Version

1.7.6

OS

MacOS

[holroy]

I'm not sure if this qualifies as a bug per se, but I can see the annoyance. In recent version of Dataview you could consider another option, and that is to increase the time before a query is refreshed, and then if needed rather trigger the command Dataview: Rebuild current view to do the refresh. You could even assign that command to a hotkey, and extend the refresh period even more.

[fcskit]

Thanks, for your answer. Is there a way to call Dataview: Rebuild current view through the dataview api? That would allow me to disable the refresh globally and set refresh intervals independently for each dataviewjs or dataview view container, if needed.

[holroy]

It's a command so you could trigger that command any way you like. Preferably though from something connected to the active view, as it'll most likely fail in other cases. You could use a button in the current document to trigger the command, but I mostly use hotkey.

If you like Commander, you could also set up a ribbon icon to trigger the command, so there are many options. I'm not sure if I would link it to the document directly, as that might trigger a multitude of potential refreshes all over your vault, which again might lead to some instability issues.