Bug 1023423

Summary:	[RFE] resize to maximum satisfiable dimension when some of requested dimensins exceed them
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	David Jaša <djasa>
Component:	RFEs	Assignee:	David Blechter <dblechte>
Status:	CLOSED WONTFIX	QA Contact:	Shai Revivo <srevivo>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	cfergeau, dblechte, ecohen, gklein, iheim, lpeer, marcandre.lureau, pvine, rbalakri, sherold, yeylon
Target Milestone:	---	Keywords:	FutureFeature, Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	spice
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-22 15:47:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Spice	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description David Jaša 2013-10-25 11:39:00 UTC

Description of problem:
resize to maximum satisfiable dimension when some of requested dimensins exceed them. This is a kind of follow-up to bug 863488 - when user resizes the window in a way that one or both dimensions exceed maximum resolution supported by driver, no resize occurs. IMO the resolution should be changed to maximum that can be set - [x = min(requested_x, maximum_supported_x), y = min(requested_y, maximum_supported_y)].

Version-Release number of selected component (if applicable):
qxl-win-0.1-19

How reproducible:
always

Steps to Reproduce:
1. resize window so that x dimension of spice widget exceeds 2560 (or actual maximum x dimension at time of verification) and y dimension changes within supported limits
2.
3.

Actual results:
no resolution change takes place

Expected results:
x is resized to 2560
y is resized to desired size

Additional info:

Comment 2 Marc-Andre Lureau 2014-08-11 17:44:21 UTC

I think it should be an RFE, it sounds like a nice idea however

It's not obvious for the agent to know the reason of failure, and it doesn't know the max size of the surface0 either. It will be a bit tricky to keep aspect ratio. Getting a resolution that is not what you requested might be worse than keeping currently working configuration.(imagine off by 1, you get scaling artefact, and it's hard to tell if it's device fault or client fault etc). I am marking this as conditional devel nack for now.

Comment 3 RHEL Program Management 2014-08-11 17:46:11 UTC

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.

Comment 4 David Blechter 2014-08-11 17:53:49 UTC

moving to the RFEs component

Comment 6 Itamar Heim 2015-03-22 15:47:08 UTC

Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.