You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Usually this should not happen via the GUI as the default file list parser only include supported image formats in the resulting file list. However, in the preferences now we have an option to show all files so the file list can have all other unsupported files such as pdf, png, etc. Then if we single click on one, the file info shows it is unsupported as expected. However, if we double-click on one, the backend crashes...
To Reproduce
Steps to reproduce the behavior:
set the "file list" dropdown menu in the "Global" tab of the preferences dialog to "all files"
navigate to a folder with unsupported image formats, such as png or pdf
single-click on one and backend should return an error message and the frontend shows it in the file info
double-click on one and the backend should crash
Expected behavior
Backend should not crash in this case and it should also throw an error to the frontend.
Platform info (please complete the following information):
OS [e.g. macOS Monterey]: macOS Monterey
Browser [e.g. chrome, safari, electron app]: chrome
Browser version [e.g. 22]: 103
Backend branch [e.g. dev, v3b2 release]: dev
Frontend branch [e.g. dev, v3b2 release]: dev
The text was updated successfully, but these errors were encountered:
Describe the bug
Usually this should not happen via the GUI as the default file list parser only include supported image formats in the resulting file list. However, in the preferences now we have an option to show all files so the file list can have all other unsupported files such as pdf, png, etc. Then if we single click on one, the file info shows it is unsupported as expected. However, if we double-click on one, the backend crashes...
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Backend should not crash in this case and it should also throw an error to the frontend.
Platform info (please complete the following information):
The text was updated successfully, but these errors were encountered: