Skip to content
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

File description is used like a program name in Windows #6

Closed
BenjaminRi opened this issue Nov 27, 2022 · 4 comments
Closed

File description is used like a program name in Windows #6

BenjaminRi opened this issue Nov 27, 2022 · 4 comments

Comments

@BenjaminRi
Copy link
Owner

BenjaminRi commented Nov 27, 2022

https://stackoverflow.com/questions/15495613/correct-usage-of-the-versioninfo-resource

Example error dialog

It is up for debate whether we should put the application name or the description (like I have done in 3cf2f62) into that field . See also: mxre/winres#43

@zedseven
Copy link
Contributor

I think the application name should be used for FileDescription, since that property is what's used as the program name in Task Manager.

@BenjaminRi
Copy link
Owner Author

Yeah, it's weird when a sentence describing what the program does is inserted in places where you'd expect a name (as in the screenshot above). I should probably fix this and also redo the pictures in the README.md.

@BenjaminRi
Copy link
Owner Author

I did some more research on this, and other toolkits faced the exact same problem, with the timeline being:

If we were to apply the current logic to ripgrep, it would look like this:

Screenshot_20241128_083029

That's clearly wrong, so it has to be fixed here in the winresource crate. The FileDescription must be the package name.

@BenjaminRi
Copy link
Owner Author

Fixed in 0921b8a (Use package name as FileDescription because Windows uses FileDescription as application name in tools and dialogs.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants