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
I'm not sure if this is even possible, or if it's up to the Operating System, but I have two monitors and when the sudo pop-up opens when I'm editing a file, the dialog box opens on the other monitor (the primary one in Windows 10 settings). Would it be possible to force the dialog box pop-up to open on the same monitor as where the snowflake app is running? I totally understand if that is not something you can control.
The text was updated successfully, but these errors were encountered:
I'm not sure if this is even possible, or if it's up to the Operating System, but I have two monitors and when the sudo pop-up opens when I'm editing a file, the dialog box opens on the other monitor (the primary one in Windows 10 settings). Would it be possible to force the dialog box pop-up to open on the same monitor as where the snowflake app is running? I totally understand if that is not something you can control.
when it comes to tech, i feel if we can think it we can probably see it through. we stop growing as techs when we stop thinking what can or may be possible. me and a friend of mine have polar opposite ideas in this, he refuses to believe that anything he cannot hack into can even be hacked at all, however i am very very stubborn and enjoy poking at the exploits and finding a new vuln. so :) i wish to think anything is possible in this art and industry
I'm not sure if this is even possible, or if it's up to the Operating System, but I have two monitors and when the sudo pop-up opens when I'm editing a file, the dialog box opens on the other monitor (the primary one in Windows 10 settings). Would it be possible to force the dialog box pop-up to open on the same monitor as where the snowflake app is running? I totally understand if that is not something you can control.
The text was updated successfully, but these errors were encountered: