This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Active windows corner not working for top left

Tags: None
(comma "," separated)
ashmikuz
Registered Member
Posts
9
Karma
0
OS
All other corners seem to work well, but the top left one does not. I cannot seem to understand where the configuration of those corners is, it doesn't seem to be in kwinrc. I am using kde 4.8 from experimental in debian sid (yes I know, because of this I should not complain...). The rest of kde 4.8 works perfectly, so I hope I can solve this last tiny problem...
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
You should be able to change this behaviour in System Settings > Workspace Behaviour > Screen Edges.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
ashmikuz
Registered Member
Posts
9
Karma
0
OS
That's exactly what i did... But all the screen edges work except the one i usually use....
mgraesslin
KDE Developer
Posts
572
Karma
7
OS
which action have you configured for the edge?
ashmikuz
Registered Member
Posts
9
Karma
0
OS
None of them works, but I needed present windows (don't know if this is the exact english translation...)
ashmikuz
Registered Member
Posts
9
Karma
0
OS
I foundout these are the configurations for the borders, and thee active one is exactly the one i chosen, number 7. Is there some other configurations/something I should check?
Code: Select all
[Effect-PresentWindows]
BorderActivate=9
BorderActivateAll=7
TabBox=false
TabBoxAlternative=false
luebking
Karma
0
- Multiscreen setup?
- are there (autohidin) panels in the corner that do not touch other corners?
ashmikuz
Registered Member
Posts
9
Karma
0
OS
No it seems to me I have only one panel. I tried looking for strange stuff, and the only one I could find was this in plasma-desktoprc:
Code: Select all
[PlasmaViews][1]
panelVisibility=0

[PlasmaViews][1][Sizes]
lastsize=1920

[Updates]
performed=/usr/share/kde4/apps/plasma-desktop/updates/addShowActivitiesManagerPlasmoid.js,/usr/share/kde4/apps/plasma-desktop/updates/systray-to-notifications-widget.js

[ViewIds]
1=1
8=2

Why is panel visibility set to 0? Weird....
luebking
Karma
0
You didn't say whether it's a multiscreen setup ;-)
Ok, run "konsole", call
xprop > corner.props
the cursor will turn into a cross, move it to the corner (after having sth. that works in other corners but not here, configured there) and click
then do the very same for
xwininfo > corner.info

in the end you'll have two files corner.props & corner.info that you can paste at pastebin or so and post here (or, if the content is very short, you can just post it here directly)
ashmikuz
Registered Member
Posts
9
Karma
0
OS
Thanks for the tip. No multescreen, I admit I forgot to mention that. The xprop output is very short, and it is the same for the corners that are working and the only one that's not:
Code: Select all
XdndAware(ATOM) = ATOM

The xwininfo out is a little bit longer, so I post it on pastebin: http://pastebin.com/8V5QeSNd
I also tested the top right corner that's working, the only difference seems to me the coordinates of the pointer and the order of the corners in the penultimate line of the output.
ashmikuz
Registered Member
Posts
9
Karma
0
OS
I made some more tests. I discovered that also the top - middle side does not work, as well as the middle-left one.
The weirdest thing is that if I enable all the corners, they all work excepting the top-right one. If I enable one of the middle sides that do not work, the nearby corners stop working, even those that were working before... For example, if I enable top right corner, it works. If i then enable the top side, the rop right stops working... Really weird...
luebking
Karma
0
I can confirm that activating a corner if the adjacent edges are assigned is quite hard.
This is likely because the enter events are lost when you cross from one electric border window to another - as a consequence you'd have to hit the corner pixel precise (ie. w/o walking alongside one of the adjacent edges before) what is close to impossible (unless you wasted your youth to <place random shooter here>)
ashmikuz
Registered Member
Posts
9
Karma
0
OS
I created a rather small bash script to make some tests "moving" the mouse pointer automatically, to see if I could track the problem better. I also made the command print the coordinates of the pointer with xdottool. This is the script:
Code: Select all
#!/bin/bash
for i in `seq 1 100`; do
        xte 'mousemove 0 0'; xdotool getmouselocation;
done

When I run it, the present window effect gets triggered once every ~20 times(4/5 times in 100). Then after a couple seconds the effect is "closed". The weirdest thing is that the mouse coordinates for xdtool getmouselocation are 1 1 instead of 0 0. If I move the pointer to the border it says 0 0, but the script does not appear to be able to move it to the "origin"...
luebking
Karma
0
Nothing weird here, move along ;-)
KWin pushes back the mouse to track activity (ie. enable the timeout, figure whether the user really wants to push the mouse there) - so when xdotool prints the mouse has just been pushed by by 1,1 px
It's also expected that in == out ie, the corner that activates an effect also deactivates it.
The (configurable) activation and reactivation delay also limit the amount of re/activations in a time (so does the event processing precision)
K4LiN
Registered Member
Posts
2
Karma
0
I have same issue, but left side won't work only when I try to use it by touchpad. Work's fine for pluged mouse and trackpoint. Also corners work just fine, if I don't set anything on the middle left side switch and don't turn on switch destktop on the edge. Else the corners, and all left edge won't work for touchpad. I'm using autohide left panel, and it' doesn't apear to. Again, for mouse and trackpoint everything works just fine.

EDIT: Also when middle left or switch desktop is set, autohide panel sometimes won't apear even on mouse.


Bookmarks



Who is online

Registered users: abc72656, Bing [Bot], daret, Google [Bot], Sogou [Bot], Yahoo [Bot]