Hello,
I thought about it and I don't think it's an issue.
If I understand correctly, all screens of multiple monitor setup share
single frame buffer. So screen size is best way to determine size for
rendering part of dwm on one of screens. To make it work in my case
it would have to be intersect
* sek...@posteo.se [09.08.2017 08:55]:
I tried this command, but adjusted it for my screen and set the real dimension
to the --fb switch.
xrandr --fb 1920x1080 --output VGA-1 --auto --transform 1,0,-168,0,1,0,0,0,1
It works perfectly!
Ah damn, that was too fast, sorry. I misread your messag
* Kajetan Jasztal [08.08.2017 12:50]:
Hi,
my laptop's screen broke lately and I've got about 168px column
on left unusable, this xrandr command seems to work, ie it crops
screen to working area
xrandr --fb 1432x900 --output eDP1 --auto --transform 1,0,-168,0,1,0,0,0,1
but dwm renders on full
Hi Kajetan,
On 8 August 2017 at 12:49, Kajetan Jasztal wrote:
> my laptop's screen broke lately and I've got about 168px column
> on left unusable, this xrandr command seems to work, ie it crops
> screen to working area
>
> xrandr --fb 1432x900 --output eDP1 --auto --transform 1,0,-168,0,1,0,0,0,
Hi,
my laptop's screen broke lately and I've got about 168px column
on left unusable, this xrandr command seems to work, ie it crops
screen to working area
xrandr --fb 1432x900 --output eDP1 --auto --transform 1,0,-168,0,1,0,0,0,1
but dwm renders on full width of screen (1600x900), so root and
o
