xpra icon
Bug tracker and wiki

Opened 3 weeks ago

Last modified 3 weeks ago

#2458 assigned enhancement

xpra shadow: on client maximize, scale the other screen "perfectly"

Reported by: stdedos Owned by: Antoine Martin
Priority: minor Milestone: 4.0
Component: client Version: 3.0.x
Keywords: Cc:

Description

Attempt to almost imitate the RDP protocol.

I would guess that changing the underlaying resolution would be way too complicated, since the monitors are attached to physical monitors.

When maximizing the client (or going full screen), attempt to scale the image perfectly to size (optionally, give the option to add black bars to avoid weird stretching).

Note that the scale "you" are doing might be better than the OpenGL scaling (text is unreadable, there are too many artifacts)

Change History (4)

comment:1 Changed 3 weeks ago by Antoine Martin

Status: newassigned

Previously discussed in #2455 where some screenshots can be found.

Note that the scale "you" are doing might be better than the OpenGL scaling (text is unreadable, there are too many artifacts)

I don't understand this bit. OpenGL scaling is not meant to give any artifacts. There may be a slight blur with non whole integer scaling, but when scaling by 200%, it should be "pixel perfect" - which just means you get jagged edges.

comment:2 Changed 3 weeks ago by Antoine Martin

Component: androidclient

comment:3 in reply to:  1 Changed 3 weeks ago by stdedos

Replying to Antoine Martin:

Previously discussed in #2455 where some screenshots can be found.

Note that the scale "you" are doing might be better than the OpenGL scaling (text is unreadable, there are too many artifacts)

I don't understand this bit. OpenGL scaling is not meant to give any artifacts. There may be a slight blur with non whole integer scaling, but when scaling by 200%, it should be "pixel perfect" - which just means you get jagged edges

Apologies, I keep forgetting to mention everything all the time 😅.

My usecase is scaling down, not up. (Q)HD to 1366x768 screen

comment:4 Changed 3 weeks ago by Antoine Martin

My usecase is scaling down, not up. (Q)HD to 1366x768 screen

Right, in that case you also need #2052 to save tons of network traffic and use a high quality downscaling algorithm.

Note: See TracTickets for help on using tickets.