Created:
20th November, 2008

It’s bug hunting time!

Just like all other mainline KDE projects, KWin has hit hard freeze. This means that we will be concentrating solely on bugs from now until the end of January which is when KDE 4.2 will be released.

Since last time:

Comments

20th November, 2008Tom Mann

http://www.pouet.net/topic.php?which=5495&page=1

I came across this which is more of a rant but could be a starter…

20th November, 2008D.J. Capelis

Not to be pushy, but this kwin (presumably?) bug I submitted recently seems like it could be a really quick fix if you’re in the mood to close reports: https://bugs.kde.org/show_bug.cgi?id=173544

 :)?

Oh and here’s a few more things if you get really motivated. I run a dual-monitors setup where the monitors have differing resolutions, so I see a lot of small bugs that relate to that: (I still use the kwin as shipped in 4.1.3 though, so it’s possible some of this stuff is fixed in trunk…)

  • The mouse pointer disappears in the area of the desktop that isn’t being displayed by a monitor. Having your mouse pointer offscreen is disorienting.
  • When you move one window from one screen to another using a keyboard shortcut like I described in bug #173545 one window will happily move from the screen with a larger resolution into a screen with a smaller resolution and map part of the window completely off-screen. Not sure what it should do instead, but this seems like it isn’t entirely desirable. The other issue is that it seems like the correct behavior when the shortcut is triggered again is it should go back on the larger screen to the same place it came from, which means you’ll have to store that somehow. Either that or you can scale the location on the screen by the appropriate resolution instead of just shifting it to a different monitor at the same x/y location. That seems like the best fix.

Thanks for your hard work. :)

20th November, 2008chimai

Sweet news. Thanks for your work! :)

20th November, 2008Nathan Bradshaw

Hi Lucas, excuse the ‘dear layweb’ nature of this querstion, but just quickly… does coverflow have it’s own code for animating the images or does it come from an external lib? and if from an external lib, which one?

cheers Nathan

20th November, 2008Lucas Murray

“Not to be pushy, but this kwin (presumably?) bug I submitted recently seems like it could be a really quick fix if you’re in the mood to close reports: https://bugs.kde.org/show_bug.cgi?id=173544

There is more to that bug than meets the eye.

“The mouse pointer disappears in the area of the desktop that isn’t being displayed by a monitor. Having your mouse pointer offscreen is disorienting.”

X-related problem. This isn’t something for KWin to fix.

“does coverflow have it’s own code for animating the images or does it come from an external lib? and if from an external lib, which one?”

The cover switch effect creates its own animations by using KWin’s effect library, I’m not sure about other coverflow implementations.

20th November, 2008Nathan Bradshaw

Thanks for the reply Lucas. I was having a brief look around the other day for a lib that did c/flow and stumbled upon a Qt version, but I hadn’t had a chance to sit down and look at kwin’s implementation.

With improvements to animation apparently in the works for Qt4.5 and its increasingly broad use in widget styles, plasma as well as in kwin, I wonder what the ‘right way’ (tm) is to approach creating / re-using effects.

20th November, 2008D.J. Capelis

Ah, so I see… thanks for taking a swing at it. :)

Have your say

Markup

Because some people like to be stupid HTML is not allowed in comments, instead feel free to use the following:

  • __Bold__
  • ___Italic___
  • [Hyperlink](http://address.com)
  • [[quote source]]…[[/quote]]
  • [[code:language]]…[[/code]]

Unordered and ordered lists have each line prefixed by either a dash, asterisk, hash or a number. Your choice.

All comments are heavily moderated, if you are off-topic your comment will not be published (But I might reply by E-mail).

Be careful! Once posted you cannot edit your comment.