Forum Replies Created
-
Posts
-
So your Windows version is very decent 👍
And do you still experience the Access Violation?if yes
- close FileVoyager if it’s running
- in File Explorer, type %LOCALAPPDATA% in the path bar (keep the percent characters)
- you should land in the AppData\Local folder
- spot the FileVoyager folder and rename it to, let’s say, FileVoyager.bak
- restart FileVoyager and see if the Access Violation occurs again
if not, it means that something in FV’s app data is corrupted
let me know what is the result
I’m completely unable to reproduce this issue…
I checked for the places where this message is displayed and there’s only one place.
And the conditions to display the message is that the file doesn’t exist anymore + a Viewer has the file loaded.Can you check if in Task Manager you find some “ghost” FileVoyager.exe ?
Hi alexpc,
Could you uninstall FileVoyager and reinstall it clean ?
Also, can you tell me what Windows version you’re using ?
Thank youin advance
Yes it’s related. Will work on it. A bit difficult to troubleshoot because it doesn’t happen in my “debug” environment, only in “Release”
Hi alexpc,
This message is supposed to be shown when an item is open in the Viewer, and its underlying file has been removed/moved.
And birmally it is supposed to be shown only once per file in this situation…Can you describe a bit more ?
– Was the Viewer showing the file ?
– If yes, was the Viewer embedded in a panel, or an independent window ?Anyways, I write down a todo in my backlock to allow “Don’t show again” for some messages.
And also, thank you so much for reporting issues actively. It help me makes FileVoyager a bit more robust every time 🙏Hi alexpc,
Same behaviour here… Thanks for pointing this issue.
I’ll work on it next week and keep this thread updated.
This issue is fixed with the new release of FileVoyager (24.4.13.0) available on the Download page
After a recompilation of FV, everything works without any code change. So probably a corruption or glitch in the previous packaging. I just need to wrap up some changes I was busy with, and then will repackage and distribute the fixed version.
I’ll post in this forum when the fixed version is available.
Hi,
The issue described in OP (start up minimized) is fixed in version 24.1.20.
Hi,
The issue described in OP in solved in version 24.1.20
Hi,
The issue with Ctrl+A described in OP is now solved in version 24.1.20
You must be logged in to post a comment.