-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Bug: Unable to open files from the context menu when more then 11 are selected #16136
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
Comments
We have a hardcoded limit of 10, but I'm not sure why that is. It might have just been an artificial limitation but if anyone knows, please let me know. In the meantime, we can remove it and see what happens. |
Looks like @winston-de added that limitation which hadn't existed before in BaseLayout.cs in #4190 I have no idea why but we should be able to remove this limitation safely. |
When I was testing this (however many years ago that was), trying to open a large number of files at once would cause the computer to seize and/or crash the program. Adding a cap seemed like a better option than freezing the user's machine :) |
@winston-de are you still able to reproduce this? |
@yaira2 No; it was probably an issue when we were using UWP APIs for opening files. As a fun experiment I removed the hard stop and opened all of System32, which didn't freeze the system. However, mileage will vary based on how powerful your PC is. Worth noting that Windows will hide the open option after 15 selected files. Anyways the hard code is located at line 25 of OpenItemAction.cs |
Thank you Winston! We're going to take the chance and remove the limit. |
Description
When selecting multiple files, if more than 11 files are selected, “Open” does not appear in the context menu.
All files have the same extension. For example, when opening multiple JPG files in a photo application.
Steps To Reproduce
Requirements
More than 11 files can be selected to be open.
Files Version
3.7.0.0
Windows Version
10.0.26100.1591
Log File
debug.log
The text was updated successfully, but these errors were encountered: