[05:57] <cwillu_at_work> smspillaz, sorry to keep pinging you (once every two weeks amounts to a lot of pings given sufficient polling users), but are the lazy positioning fixes available in -proposed or such yet?
[06:45] <smspillaz> cwillu_at_work: I think so
[06:46] <cwillu_at_work> smspillaz, and if I say my windows are still moving non-lazily? :p
[06:47] <smspillaz> tell me what circumstances it happens in and I will try and have a look
[06:47] <smspillaz> I am on exam leave though
[06:48] <cwillu_at_work> smspillaz, well, effectively all circumstances; easier to describe when it works right
[06:49] <cwillu_at_work> when a new window opens, it'll move fluidly until it touches an edge, is minimized/restored, etc; at which point it moves choppily
[06:49] <cwillu_at_work> if I use my gaming mouse, it's choppy to the point of not actually updating at all while the mouse is moving
[06:49] <cwillu_at_work> on the touchpad, it's merely slow
[06:50] <cwillu_at_work> also, the mouse pointer still goes out of sync with the window when moving it rapidly
[06:50] <cwillu_at_work> i.e., if I shake the mouse a bit when dragging the title bar, the mouse pointer will end up 20-40 pixels above the window
[06:58] <cwillu_at_work> also, when moving a "slow" window, the whole screen locks to the same framerate: if I'm watching a movie and move a terminal window, the movie window will only update when the terminal window appears at the new location.  On the mouse I mentioned before, I can prevent anything on the screen from updating for as long as I like by continuing to move the mouse
[07:10] <jo-erlend> yes, I've seen this too, but not often and I have no idea why it happens.
[07:11]  * cwillu_at_work jumps up and down at smspillaz 
[07:11] <cwillu_at_work> see!  see!  I'm not crazy!
[07:16] <jo-erlend> :)
[07:18] <cwillu_at_work> (right?)
[11:53] <smspillaz> cwillu_at_work: sorry, I'm just really tired right now
[11:54] <cwillu_at_work> no worries
[11:54] <smspillaz> (had a nap)
[11:54] <cwillu_at_work> there's a pill for that :p
[11:54] <smspillaz> yeah uh
[11:55] <smspillaz> had a bit of a caffeine freak-out last week
[11:55] <smspillaz> need to avoid that for a while
[11:55] <cwillu_at_work> there's... a healthier pill than that...
[11:55] <cwillu_at_work> anyways :p
[11:55] <cwillu_at_work> also, black tea;  has extra goodness that takes the edge off the caffeine
[12:05] <cwillu_at_work> smspillaz, is this still kinda sorta a known problem (in the sense of you've got a pretty good idea why it's still doing it despite the recent fixes)?
[12:06] <cwillu_at_work> if it's a known quantity, I won't bother diving into the code again, but if it's a mystery at this point, I will (if only to gain some diagnostic info that might give you an idea what's going wrong)
[12:13] <smspillaz> cwillu_at_work: I know why it happens, but it is annoying to trace down
[12:13] <smspillaz> because the API is broken in a certain sense
[12:14] <cwillu_at_work> smspillaz, this is what happens when you implement a shell as a compiz plugin? :p
[12:14] <smspillaz> it will be fixed properly for P when I finish my work to add proper plugin position offsets
[12:14] <smspillaz> cwillu_at_work: no, not really, this has always been a problem for compiz
[12:14] <smspillaz> it just manifested itself in different ways before
[12:15] <cwillu_at_work> fair enough
[12:16] <cwillu_at_work> however, I would like you to imagine that every time you ever moved a window, you couldn't see where it was going until you dropped it :p
[12:16] <smspillaz> I have seen this before
[12:20] <cwillu_at_work> smspillaz, don't you hate that feeling when you really really want to yell at somebody, but there's nobody around with a sufficient share of guilt for them to deserve it? ;p
[12:25] <smspillaz> meh
[12:25]  * smspillaz gets paid to be yelled at
[12:25] <smspillaz> I only code for fun
[12:27] <cwillu_at_work> I mean this more in a "futility" sense
[12:27] <smspillaz> I'll check what's in proposed
[12:32] <smspillaz> cwillu_at_work: its not in proposed yet
[12:32]  * cwillu_at_work sputters politely :p
[12:33] <cwillu_at_work> get some sleep
[12:34] <smspillaz> cwillu_at_work: you can build what *will* be in proposed in a few days (probably when didrocks gets back from uds), with something like
[12:34] <smspillaz> bzr branch lp:~smspillaz/compiz/compiz.SRU1-1
[12:34] <cwillu_at_work> okay
[12:35]  * cwillu_at_work got lost in a maze of bzr branches a few weeks ago
[12:36] <smspillaz> cd compiz.SRU1-1
[12:36] <smspillaz> bzr bd
[12:36] <smspillaz> cd ../build-area
[12:36] <smspillaz> dpkg -i *.deb
[12:38]  * cwillu_at_work builds
[12:42] <cwillu_at_work> building on an atom processor is fun!
[13:09]  * cwillu_at_work installs
[13:09]  * cwillu_at_work uninstalls compiz-kde... :/
[13:10]  * cwillu_at_work reboots
[13:10] <cwillu_at_work> (because I felt like it)
[13:14] <cwillu_at_work> smspillaz, nack
[13:15] <cwillu_at_work> smspillaz, movement still gets choppy, and I can still get the mouse cursor out of sync with the window when dragging it around
[13:15]  * om26er confirmes
[13:16] <cwillu_at_work> om26er, you just build from that branch as well?
[13:16] <om26er> oh no, oops just the general case :/
[13:59] <mhr3> kamstrup, for example i was talking to david and he said that he has to do the filters-changed and stripping magic in each and every scope
[13:59] <kamstrup> mhr3: i guess the heart of the issue is that we ought to capture the filter state into the LensSearch, right?
[13:59] <mhr3> yea, that would be nice
[14:00] <kamstrup> mhr3: incidentally, the upcoming tree-index branch of dee includes a DeeAnalyzer which has powerful text processing capabilities :-)
[14:00] <mhr3> i would sure like to see that easily integrate-able there :)
[14:03] <kamstrup> mhr3: the question is if we can meaningfully capture the state of the filters when we create the LensSearch...
[14:03] <kamstrup> mhr3: I am not sure we can...
[14:05] <mhr3> i need to look at it
[15:31] <Amaranth> dang, no DBO or jaytaoko to poke to look at my merge request ;)
[21:31] <beevvy> Hi. I sent a message titled "Unity global menu and Qt" to the ayatana-dev ml this Monday. Why it isn't shown in the list's public archive?