Forum Replies Created
-
Posts
-
And I suppose you have recovered all your settings, because I gave you the wrong environement variable.
FV settings are actually stored in %APPDATA%, not %LOCALAPPDATA%.Fortunately, this error worked in your favor: your settings were preserved, and the Access Violation issue has been resolved. 😉
I will mark this topic as [RESOLVED]. However, please don’t hesitate to create a new topic or post here again if the issue reoccurs.
I’m able to reproduce the display of the warning message, but only once, which is the normal behaviour. I’m not able to reproduce the multiple overlapping warnings.
Anyways, I’ll plan to add a mechanism (checkbox) to “remember” the answers of a certain set of messages and record those answers in the ini file.
I’ll keep this thread updated
Note that, by doing the above, you’ll restart FV without you personalisation.
wéll see together how to recover most of your settings.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
You must be logged in to post a comment.