Bug 347027 - double click on window title does not expand window to full screen
Summary: double click on window title does not expand window to full screen
Status: RESOLVED DUPLICATE of bug 345473
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.3.0
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-01 21:43 UTC by m.wege
Modified: 2015-05-03 11:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description m.wege 2015-05-01 21:43:59 UTC
I have just switched from to KDE5 (on Kubuntu 15.04). On KDE 4, I could double click on the window title and it expanded full screen. This does not work anymore with KDE5 even though  system settings->window behaviour -> window title->double click is set to maximize. When I double click, the mouse curse changes for a second into a cross like cursor.

May be it has something to do with the fact that I have a dual monitor configuration.

Reproducible: Always
Comment 1 Thomas Lübking 2015-05-01 21:52:07 UTC
might be related to bug #346889

can you please attach ~/.config/kwinrc ?
Comment 2 m.wege 2015-05-01 21:53:51 UTC
(In reply to Thomas Lübking from comment #1)
> can you please attach ~/.config/kwinrc ?
here it is:

[Compositing]
OpenGLIsUnsafe=false

[Desktops]
Number=1

[Effect-Zoom]
InitialZoom=1

[org.kde.kdecoration2]
BorderSize=Tiny
ButtonsOnLeft=MS
ButtonsOnRight=HIAX
CloseOnDoubleClickOnMenu=false
library=org.kde.breeze
Comment 3 Thomas Lübking 2015-05-01 22:14:19 UTC
mhh-hmmm.

"kcmshell5 kwinoptions", does that indicate you're maximizing on doubleclick?
if yes, please alter it to something else and check ~/.config/kwinrc again - is there now an entry eg.

[Windows]
...
TitlebarDoubleClickCommand=Shade
... ?
Comment 4 m.wege 2015-05-01 23:44:42 UTC
did as advised, now it looks like this:
[Compositing]
OpenGLIsUnsafe=false

[Desktops]
Number=1

[Effect-Zoom]
InitialZoom=1

[MouseBindings]
CommandActiveTitlebar1=Raise
CommandActiveTitlebar2=Start window tab drag
CommandActiveTitlebar3=Operations menu
CommandAll1=Move
CommandAll2=Toggle raise and lower
CommandAll3=Resize
CommandAllKey=Alt
CommandAllWheel=Nothing
CommandInactiveTitlebar1=Activate and raise
CommandInactiveTitlebar2=Start window tab drag
CommandInactiveTitlebar3=Operations menu
CommandTitlebarWheel=Switch to Window Tab to the Left/Right
CommandWindow1=Activate, raise and pass click
CommandWindow2=Activate and pass click
CommandWindow3=Activate and pass click
CommandWindowWheel=Scroll

[Plugins]
windowgeometryEnabled=false

[Windows]
ActiveMouseScreen=false
AutoRaise=false
AutoRaiseInterval=750
AutogroupInForeground=true
AutogroupSimilarWindows=false
BorderSnapZone=10
CenterSnapZone=0
ClickRaise=true
DelayFocusInterval=300
FocusPolicy=ClickToFocus
FocusStealingPreventionLevel=1
GeometryTip=false
HideUtilityWindowsForInactive=true
InactiveTabsSkipTaskbar=false
MaximizeButtonLeftClickCommand=Maximize
MaximizeButtonMiddleClickCommand=Maximize (vertical only)
MaximizeButtonRightClickCommand=Maximize (horizontal only)
NextFocusPrefersMouse=false
Placement=Smart
SeparateScreenFocus=false
ShadeHover=false
ShadeHoverInterval=250
SnapOnlyWhenOverlapping=false
TitlebarDoubleClickCommand=Maximize
WindowSnapZone=10

[org.kde.kdecoration2]
BorderSize=Tiny
ButtonsOnLeft=MS
ButtonsOnRight=HIAX
CloseOnDoubleClickOnMenu=false
library=org.kde.breeze

behaviour has not changed.
Comment 5 Thomas Lübking 2015-05-02 08:02:13 UTC
Ok, config is written (and probably read) in the correct location, also "Maximize" is the default.
Let's assume this works, you could also try other settings for confirmation (eg. the mousewheel setting)

I noticed that the decoration does not honor the system wide drag start offsets (time/distance)

=> What you describe (cursor change) seems like a degenerated move, do you maybe have trouble to perform a "clean" doubleclick (ie. w/o accidentally moving the pointer, common issue on touchpads)?
Comment 6 Thomas Lübking 2015-05-03 11:51:59 UTC
There seems an issue with the doubleclick event.

*** This bug has been marked as a duplicate of bug 345473 ***