Persistence of the "Offline Edits" Dialog When Closing RDM
Persistence of the "Offline Edits" Dialog When Closing RDM
1 vote
Description:
Currently, offline edits are discarded when the "Offline Edits" dialog is closed via the "X" button or when RDM is forcefully closed. This can lead to unintentional data loss, especially if the dialog is open on an unseen monitor and the user is unaware of it.
Proposed Improvement:
The "Offline Edits" dialog should reappear the next time the user goes online if no explicit decision has been made (either to discard or accept the changes). Offline edits should be preserved until the user actively makes a choice.
Benefits:
- Prevents accidental loss of offline edits.
- Enhances user experience by ensuring changes are not unintentionally lost.
- Increases transparency by avoiding unnoticed pending edits.
Thank you for considering this suggestion!
All Comments (6)
Odd, I will have to double check, but in theory hitting the X should be considered like doing cancel (aka stay offline) and not cause any data lost. I will investigate further.
What version are you seeing this on?
Best regards,
Stéfane Lavergne
The whole offline behavior with Devolutions Hub is so weird. I can't tell you the number of times I've been like "Why won't this let me Edit/Duplicate" only to poke around for awhile to eventually realize I'm offline. I think it should be clearer that you are offline and offer an option that involves attempting to go online when you access an "online only" feature. I'd say this happens about 80% of the time because I've closed my laptop and the network has "fallen asleep".
In theory, only user actions should lead to RDM going offline, and there should always be a prompt. Everything else should silently fail but remain "online." For example, "auto-refresh" should not put you offline—it should fail, log or ignore the error, and try again at the next auto-refresh interval. A manual refresh (F5), for instance, should fail and then prompt the user, asking whether to go offline or not.
Like I said, this is in theory. I’ll need to investigate further to see what might have changed to cause this behavior.
Best regards,
Stéfane Lavergne
only user actions should lead to RDM going offline
I guess closing the laptop lid could be considered a user action. But I've never deliberately told the app to go into Offline mode on my M1 Macbook Pro and I would say it is in Offline mode about once every 36 hours. Happy to do some troubleshooting on that with support if there are recommendations on how to "catch it in action".
Odd, I will have to double check, but in theory hitting the X should be considered like doing cancel (aka stay offline) and not cause any data lost. I will investigate further.
What version are you seeing this on?
Best regards,
Hi, thanks for the quick response. I tested RDM’s behavior again. When I close the "Offline Edits" dialog using the X button, RDM remains in offline mode. However, if I close RDM via Task Manager while the "Offline Edits" window is still open, I lose my offline-saved entries. It seems that force-closing RDM through Task Manager creates a new offline cache?
We are using version 2024.3.29.0 64-bit.
Oh, I see. Yeah, if you kill the app while the Offline Edits window is open, you will lose your changes. For now, that's by design.
You see, when you go back online, we extract your offline changes, put them into memory, clear the offline data (full refresh), reload the data, check for conflicts, pop the sync window, and then—depending on the outcome—we either save the changes, reapply them to the offline store, or throw them out. So while the window is up, you’re vulnerable to losing your data.
We could, in theory, reapply them before the window pops up and then adjust according to the outcome.
Even then, if you were to kill the app at just the right moment, you could still lose data. I think the same could be said for a lot of apps—killing an app usually puts it in an undefined state.
Stéfane Lavergne