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
The size and position of the ArmCord-Win7 window is not remembered between application launches. Window is default cramped tiny 835x600 in center of primary monitor on every launch.
To Reproduce
Steps to reproduce the behavior:
Launch ArmCord-Win7
Resize and move window
Close ArmCord-Win7
Launch ArmCord-Win7
Observe that window size and position were not remembered
Expected behavior
Window size and position are remembered between launches. Standard Windows paradigm. The official Discord desktop application does this.
Desktop (please complete the following information):
OS: Windows 7
Method of installation: standalone release from this repo
Version: 3.3.4
Additional context
I have no clue if upstream ArmCord also has this failure and thus would this be their fault. I've never used ArmCord before until right now.
Vesktop is the same concept as ArmCord and successfully remembers window size and position between launches, though it only cares about bugcrash 10.
The text was updated successfully, but these errors were encountered:
Describe the bug
The size and position of the ArmCord-Win7 window is not remembered between application launches. Window is default cramped tiny 835x600 in center of primary monitor on every launch.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Window size and position are remembered between launches. Standard Windows paradigm. The official Discord desktop application does this.
Desktop (please complete the following information):
Additional context
I have no clue if upstream ArmCord also has this failure and thus would this be their fault. I've never used ArmCord before until right now.
Vesktop is the same concept as ArmCord and successfully remembers window size and position between launches, though it only cares about bugcrash 10.
The text was updated successfully, but these errors were encountered: