-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: When a ZIP file is opened via file association, the Extract Button is not displayed on the toolbar #15457
Comments
Thank you for the report |
Just noticed an update is available, so I updated to 3.4.1.0 and problem remains. |
I would like to solve this. Can I know where the AddressToolbarViewModel gets its Data from? |
AddressToolBarViewModel is called twice once for Home and second time for the zip file. CanExtract is true for the zip file, but I think it overrides its CanExtract with Home. |
So after some debugging, I think that once the new tab is open into a zip file, Update_ViewModel is not being called immediatly, and only waits till there is a chance (the mouse hovering over). This bug also appears when you simple right clip open a zip file. I think I can fix this, but when exactly is this function called? I was having trouble tracing the call stack |
It might be the selected item property. |
I mean I want to know what actions trigger Update_ViewModel. Basically, I don't know if there is an event handler for when the application moves from one folder into another. The stage change seems to only trigger just before we enter the folder, and not after. But I do not know how to change or check this |
Description
I have Files set as my default handler for Zip files. When I download a zip file in MS Edge and then open that zip file from Edge, Files is opened as expected, but the Extract button is not visible.
If Files loses focus and regains focus, the extract button will show up on the refresh.
Steps To Reproduce
Requirements
At step 4, the Extract button should be visible.
Files Version
3.4.0.0
Windows Version
10.0.22621.3593
Log File
debug.log
The text was updated successfully, but these errors were encountered: