Create intentional border with xrandr
Is there a way to tell xrandr "this space intentionally left blank"?
I have a laptop that drives its internal display at 1920x1080, but the external monitor I'm using, due to its different aspect ratio, doesn't have that mode. It runs at 1920x1200.
So, the basic setup:
xrandr
--output LVDS-1 --mode 1920x1080
--output DP-1 --mode 1920x1200 --same-as LVDS-1
[not to scale:]
┌─────────────────┬─────────────────┐
│ │ │
│ (laptop) │ (external) │
│ (LVDS-1) │ (DP-1) │
│ │ │
│ │ │
└─────────────────┤ │
(blank...) │ │
└─────────────────┘
How can I specify that the 1920x120-sized region below LVDS-1 should be displayed as a black bar that can't be accessed by mouse on DP-1?
I tried just coping with --panning 1920x1200+0+0/1920x1080+0+0/0/0/0/120, but I found the screen movement to be very annoying.
Update:
I found a workaround. (Update 2: changed it to an answer, per suggestion -- workaround doesn't answer the underlying question of leaving space blank.)
xrandr
asked Oct 1 '12 at 16:57
benizibenizi
447414
add a comment |
Is there a way to tell xrandr "this space intentionally left blank"?
I have a laptop that drives its internal display at 1920x1080, but the external monitor I'm using, due to its different aspect ratio, doesn't have that mode. It runs at 1920x1200.
So, the basic setup:
xrandr
--output LVDS-1 --mode 1920x1080
--output DP-1 --mode 1920x1200 --same-as LVDS-1
[not to scale:]
┌─────────────────┬─────────────────┐
│ │ │
│ (laptop) │ (external) │
│ (LVDS-1) │ (DP-1) │
│ │ │
│ │ │
└─────────────────┤ │
(blank...) │ │
└─────────────────┘
How can I specify that the 1920x120-sized region below LVDS-1 should be displayed as a black bar that can't be accessed by mouse on DP-1?
I tried just coping with --panning 1920x1200+0+0/1920x1080+0+0/0/0/0/120, but I found the screen movement to be very annoying.
Update:
I found a workaround. (Update 2: changed it to an answer, per suggestion -- workaround doesn't answer the underlying question of leaving space blank.)
xrandr
asked Oct 1 '12 at 16:57
benizibenizi
447414
Please consider posting the workaround as answer. You don't have to accept it, and can still point out the flaws, but it's more discoverable that way.
– Daniel Beck♦
Oct 2 '12 at 8:10
add a comment |
Is there a way to tell xrandr "this space intentionally left blank"?
I have a laptop that drives its internal display at 1920x1080, but the external monitor I'm using, due to its different aspect ratio, doesn't have that mode. It runs at 1920x1200.
So, the basic setup:
xrandr
--output LVDS-1 --mode 1920x1080
--output DP-1 --mode 1920x1200 --same-as LVDS-1
[not to scale:]
┌─────────────────┬─────────────────┐
│ │ │
│ (laptop) │ (external) │
│ (LVDS-1) │ (DP-1) │
│ │ │
│ │ │
└─────────────────┤ │
(blank...) │ │
└─────────────────┘
How can I specify that the 1920x120-sized region below LVDS-1 should be displayed as a black bar that can't be accessed by mouse on DP-1?
I tried just coping with --panning 1920x1200+0+0/1920x1080+0+0/0/0/0/120, but I found the screen movement to be very annoying.
Update:
I found a workaround. (Update 2: changed it to an answer, per suggestion -- workaround doesn't answer the underlying question of leaving space blank.)
xrandr
asked Oct 1 '12 at 16:57
benizibenizi
447414
Is there a way to tell xrandr "this space intentionally left blank"?
I have a laptop that drives its internal display at 1920x1080, but the external monitor I'm using, due to its different aspect ratio, doesn't have that mode. It runs at 1920x1200.
So, the basic setup:
xrandr
--output LVDS-1 --mode 1920x1080
--output DP-1 --mode 1920x1200 --same-as LVDS-1
[not to scale:]
┌─────────────────┬─────────────────┐
│ │ │
│ (laptop) │ (external) │
│ (LVDS-1) │ (DP-1) │
│ │ │
│ │ │
└─────────────────┤ │
(blank...) │ │
└─────────────────┘
How can I specify that the 1920x120-sized region below LVDS-1 should be displayed as a black bar that can't be accessed by mouse on DP-1?
I tried just coping with --panning 1920x1200+0+0/1920x1080+0+0/0/0/0/120, but I found the screen movement to be very annoying.
Update:
I found a workaround. (Update 2: changed it to an answer, per suggestion -- workaround doesn't answer the underlying question of leaving space blank.)
xrandr
xrandr
asked Oct 1 '12 at 16:57
benizibenizi
447414
asked Oct 1 '12 at 16:57
benizibenizi
447414
edited Oct 2 '12 at 8:37
benizi
asked Oct 1 '12 at 16:57
benizibenizi
447414
asked Oct 1 '12 at 16:57
benizibenizi
447414
asked Oct 1 '12 at 16:57
benizibenizi
447414
447414
Please consider posting the workaround as answer. You don't have to accept it, and can still point out the flaws, but it's more discoverable that way.
– Daniel Beck♦
Oct 2 '12 at 8:10
add a comment |
Please consider posting the workaround as answer. You don't have to accept it, and can still point out the flaws, but it's more discoverable that way.
– Daniel Beck♦
Oct 2 '12 at 8:10
Please consider posting the workaround as answer. You don't have to accept it, and can still point out the flaws, but it's more discoverable that way.
– Daniel Beck♦
Oct 2 '12 at 8:10
Please consider posting the workaround as answer. You don't have to accept it, and can still point out the flaws, but it's more discoverable that way.
– Daniel Beck♦
Oct 2 '12 at 8:10
add a comment |
1 Answer
1
active
oldest
votes
I found a workaround in a discussion about aspect ratios under Compiz (a variant on option #2):
xrandr --fb 1920x1080
--output LVDS-1 --mode 1920x1080
--output DP-1 --mode 1920x1200 --scale 1x.9
This makes the external monitor scale the image. I'm not sure the --fb 1920x1080 (which specifies the size of the virtual screen) is strictly necessary here. Possibly --pos 0x0 would supplant it.
Workaround is still pretty unsatisfying -- it only happens to work out because it's a nice, easy multiple -- it would be nice to have a more general solution.
answered Oct 2 '12 at 8:32
benizibenizi
447414
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f481978%2fcreate-intentional-border-with-xrandr%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I found a workaround in a discussion about aspect ratios under Compiz (a variant on option #2):
xrandr --fb 1920x1080
--output LVDS-1 --mode 1920x1080
--output DP-1 --mode 1920x1200 --scale 1x.9
This makes the external monitor scale the image. I'm not sure the --fb 1920x1080 (which specifies the size of the virtual screen) is strictly necessary here. Possibly --pos 0x0 would supplant it.
Workaround is still pretty unsatisfying -- it only happens to work out because it's a nice, easy multiple -- it would be nice to have a more general solution.
answered Oct 2 '12 at 8:32
benizibenizi
447414
add a comment |
I found a workaround in a discussion about aspect ratios under Compiz (a variant on option #2):
xrandr --fb 1920x1080
--output LVDS-1 --mode 1920x1080
--output DP-1 --mode 1920x1200 --scale 1x.9
This makes the external monitor scale the image. I'm not sure the --fb 1920x1080 (which specifies the size of the virtual screen) is strictly necessary here. Possibly --pos 0x0 would supplant it.
Workaround is still pretty unsatisfying -- it only happens to work out because it's a nice, easy multiple -- it would be nice to have a more general solution.
answered Oct 2 '12 at 8:32
benizibenizi
447414
add a comment |
I found a workaround in a discussion about aspect ratios under Compiz (a variant on option #2):
xrandr --fb 1920x1080
--output LVDS-1 --mode 1920x1080
--output DP-1 --mode 1920x1200 --scale 1x.9
This makes the external monitor scale the image. I'm not sure the --fb 1920x1080 (which specifies the size of the virtual screen) is strictly necessary here. Possibly --pos 0x0 would supplant it.
Workaround is still pretty unsatisfying -- it only happens to work out because it's a nice, easy multiple -- it would be nice to have a more general solution.
answered Oct 2 '12 at 8:32
benizibenizi
447414
I found a workaround in a discussion about aspect ratios under Compiz (a variant on option #2):
xrandr --fb 1920x1080
--output LVDS-1 --mode 1920x1080
--output DP-1 --mode 1920x1200 --scale 1x.9
This makes the external monitor scale the image. I'm not sure the --fb 1920x1080 (which specifies the size of the virtual screen) is strictly necessary here. Possibly --pos 0x0 would supplant it.
Workaround is still pretty unsatisfying -- it only happens to work out because it's a nice, easy multiple -- it would be nice to have a more general solution.
answered Oct 2 '12 at 8:32
benizibenizi
447414
answered Oct 2 '12 at 8:32
benizibenizi
447414
answered Oct 2 '12 at 8:32
benizibenizi
447414
answered Oct 2 '12 at 8:32
benizibenizi
447414
447414
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f481978%2fcreate-intentional-border-with-xrandr%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Please consider posting the workaround as answer. You don't have to accept it, and can still point out the flaws, but it's more discoverable that way.
– Daniel Beck♦
Oct 2 '12 at 8:10