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
Currently the debugging-window will be opened with the same dimensions (width x height) every time regardless if it was resized previously or not. Because this default dimensions are not always optimal for the user's screen resolution it will be resized manually every time it is used, thus wasting time.
Whenever the window get's resized, it should store it's new size in the user's profile. If possible it should store the size per screen resolution so that every resolution the user uses has it's own size for the debugging window. This profits the use-case of a user having a laptop that is used in different set-up's (small screen when mobile, big external screen when docked).
This issue was requested in issue #11 "Question about remote path mapping".
The text was updated successfully, but these errors were encountered:
Currently the debugging-window will be opened with the same dimensions (width x height) every time regardless if it was resized previously or not. Because this default dimensions are not always optimal for the user's screen resolution it will be resized manually every time it is used, thus wasting time.
Whenever the window get's resized, it should store it's new size in the user's profile. If possible it should store the size per screen resolution so that every resolution the user uses has it's own size for the debugging window. This profits the use-case of a user having a laptop that is used in different set-up's (small screen when mobile, big external screen when docked).
This issue was requested in issue #11 "Question about remote path mapping".
The text was updated successfully, but these errors were encountered: