Client state saving, by - key bind or crash event?
Posted: Mon Feb 19, 2024 3:09 pm
When I browse EXR/HDR files, XnView often crashes, which is okay because the client is fast to reopen. The only issue is that the client's state is lost, which I guess makes sense to prevent starting the application in a state where it will fail. However, I find myself navigating to some parent directory of EXR sequences or maybe HDRI images I need to preview and then manually closing XnView and reopen it to make it save the state. This way, I know that I don’t need to navigate here again when it crashes.
My question is: Is there a way to bind a key or create a script to save the current state of the application or, better (for me), save the state on a crash event?
I am working daily with heavy file sequences, and XnView crashes for me, maybe 4-8 times per hour. So, a shortcut or automatic state-saving would be such a time saver for me.
By the way, this is not criticism. I guess that the EXR implementation is just not optimized for this use, but I find XnView a much better experience all around than something like Adobe Bridge. <3
XnView MP - 1.6.4 64-bit (Windows) - Libformat 7.170
Windows 11
My question is: Is there a way to bind a key or create a script to save the current state of the application or, better (for me), save the state on a crash event?
I am working daily with heavy file sequences, and XnView crashes for me, maybe 4-8 times per hour. So, a shortcut or automatic state-saving would be such a time saver for me.
By the way, this is not criticism. I guess that the EXR implementation is just not optimized for this use, but I find XnView a much better experience all around than something like Adobe Bridge. <3
XnView MP - 1.6.4 64-bit (Windows) - Libformat 7.170
Windows 11