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
Originally mentioned as a toga issue, when running a toga app with briefcase the app does not display the correct name in the title bar area.
Both briefcase run and briefcase package have the same issue. When the app gets ran it goes based on the exec file name and not on the name entry provided. I have not found the exact reason for this yet, from all the testing and searching I can find online, setting the name entry should be all that is needed but this is not following that for some reason.
Steps to reproduce
Run briefcase run or package and check the application title in the title bar.
Expected behavior
Shows name provided as the project_name or formal_name.
Screenshots
No response
Environment
Operating System: Ubuntu with Wayland Gnome
Python version: 3.10
Logs
Additional context
No response
The text was updated successfully, but these errors were encountered:
@yjlc-pc "Use an old and increasingly unmaintained solution" isn't really a viable fix. Wayland is where all Linux desktop software is moving, and it's the default GUI for almost every major Linux distro; we need to be able to work there.
Describe the bug
Originally mentioned as a toga issue, when running a toga app with briefcase the app does not display the correct name in the title bar area.
Both briefcase run and briefcase package have the same issue. When the app gets ran it goes based on the exec file name and not on the name entry provided. I have not found the exact reason for this yet, from all the testing and searching I can find online, setting the name entry should be all that is needed but this is not following that for some reason.
Steps to reproduce
Run briefcase run or package and check the application title in the title bar.
Expected behavior
Shows name provided as the project_name or formal_name.
Screenshots
No response
Environment
Logs
Additional context
No response
The text was updated successfully, but these errors were encountered: