Bug 335211

Summary:	[KF5] Wrong GUI information for rotated screen
Product:	[Plasma] KScreen	Reporter:	Luiz Angelo De Luca <luizluca>
Component:	common	Assignee:	Daniel Vrátil <dvratil>
Status:	CLOSED FIXED
Severity:	major	CC:	dvratil, vit
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:	http://commits.kde.org/kscreen/56d206c58fa1bae07d4393f2f38f10424878a7d7	Version Fixed/Implemented In:	5.2.1
Sentry Crash Report:

Description Luiz Angelo De Luca 2014-05-22 18:08:53 UTC

Hello,

The screen visual information is inverted.

I have this screen setup:

Screen 0: minimum 8 x 8, current 2704 x 1280, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected primary 1680x1050+1024+115 (normal left inverted right x axis y axis) 470mm x 300mm
   1680x1050      59.9 +   60.0* 
   1280x1024      75.0     60.0  
   1280x960       60.0  
   1152x864       75.0  
   1024x768       75.0     70.1     60.0  
   800x600        75.0     72.2     60.3     56.2  
   640x480        75.0     72.8     59.9  
DP-0 connected 1024x1280+0+0 left (normal left inverted right x axis y axis) 340mm x 270mm
   1280x1024      60.0 +   75.0* 
   1280x960       60.0  
   1152x864       75.0  
   1024x768       75.0     70.1     60.0  
   800x600        75.0     72.2     60.3     56.2  
   640x480        75.0     72.8     59.9  
DP-1 disconnected (normal left inverted right x axis y axis)

However, when I configure it though kscreen, it uses wrong rotation configuration. For example:

"<- 90º clockwise" shows this visual information:
 ____________
|               ||
|               ||
|               ||
|               ||
----------------

and 

-> 90º counterclockwise
 ____________
||               |
||               |
||               |
||               |
----------------

Isn't it just the opposite? In practice, I had to configure kscreen to use the inverse (clockwise instead of counterclockwise) to get it rotated left. Visually, the diagram is not like my screens are setup. I see:

 ____________    _________________________
|              ||  |                                   |
|              ||  |                                   |
|              ||  |                                   |
|              ||  |                                   | 
----------------    ===================

(configured as clockwise, normal)

While my screens are actually:
 ____________    _________________________
||               |  |                                   |
||               |  |                                   |
||               |  |                                   |
||               |  |                                   | 
----------------    ===================

Also, I don't know if an arrow is the best symbol for a rotation information. It indicates the clock pointer from 12h or 6h? If 12h, it is inverted (which might be the origin of the diagram problem). Something like a reload icon will be much better.


Reproducible: Always

Steps to Reproduce:
1.Open systemsettings
2.Open monitors
3.Rotate a screen
Actual Results:  
4.diagram is rotated to the wrong direction
5.orientation combobox icon is pointing to the wrong direction

Comment 1 Luiz Angelo De Luca 2014-06-11 16:49:16 UTC

Still present in current git version

Comment 2 Luiz Angelo De Luca 2014-10-15 21:23:39 UTC

Still present in current git version

Comment 3 Daniel Vrátil 2015-02-05 10:21:41 UTC

Git commit 56d206c58fa1bae07d4393f2f38f10424878a7d7 by Dan Vrátil.
Committed on 05/02/2015 at 10:18.
Pushed by dvratil into branch 'Plasma/5.2'.

Fix visual representation of output rotation

If the QMLOutput represents a monitor, then rotation by 90° clockwise means
we actually want to rotate the visual rectangle by 90 degrees clockwise, not
the other way around.

The KCM now visually correctly represents how you would have to rotate your
monitor in order to see content of the screen right.
FIXED-IN: 5.2.1

M  +2    -2    kcm/qml/Output.qml

http://commits.kde.org/kscreen/56d206c58fa1bae07d4393f2f38f10424878a7d7

Comment 4 Daniel Vrátil 2015-02-05 11:11:48 UTC

*** Bug 340460 has been marked as a duplicate of this bug. ***

Comment 5 Luiz Angelo De Luca 2015-03-06 16:44:48 UTC

Perfect! Thanks.