=== smorar is now known as smorar_ [07:53] good morning [07:57] greetings everybody! [08:12] oubiwann: do you know if utouch works with the wacom bamboo touch? [08:12] smspillaz: do you reproduce compiz not exiting when trying to replace it with another wm error too? [08:12] didrocks: no, it works fine [08:13] smspillaz: you use the glib mainloop branch too? [08:13] didrocks: if it wasn't exiting, I would say it would be something to do with us not catching --replace maybe? (I tried it on the glib and glibmm branch and it worked fine though) [08:13] hum [08:13] didrocks: do you get 100% CPU usage from compiz? [08:13] not 100%, but a high CPU usage from compiz, right [08:14] I think MacSlow told he got that too [08:14] seb got it for sure [08:15] didrocks, smspillaz: I don't get 100% cpu-load from coompiz [08:15] MacSlow: not that, but when you try to change to another wm, like metacity --replace, compiz hanging [08:16] didrocks, oh... that... yeah... that can happen sometimes... but recently (last week) it happened less (maybe only once iirc) [08:17] quite reproductible here [08:17] smspillaz: any thought how to debug this? ^^ [08:17] MacSlow: didrocks: probably an infinite loop. Can you attach with gdb and get a backtrace? [08:17] smspillaz: you mean, stopping the process in gdb? [08:17] you'd get something in the high 90s [08:17] didrocks: yeah, trigger the hang, go to a vt [08:18] pidof compiz suddo gdb attach ${pid} [08:18] sure [08:18] c [08:18] bt [08:18] smspillaz, if it happens again ok [08:18] I think you can set a log file too [08:18] sure [08:18] without debug symbols for now [08:18] oh ok. debug symbols would be nice ^.^ [08:18] smspillaz, but like I said I get it a lot less frequently since about a week [08:18] smspillaz: sure for now, will get one to you later :) [08:18] ok [08:19] also while you two are here [08:19] smspillaz, so don't hold you breath [08:19] I'm having this build error with unity [08:19] MacSlow: oh dw, I have tons of other bugs to fix :p [08:19] MacSlow: as I said, I get that everytime [08:19] (let me pastebin this error) [08:19] and it prevents gnome to logout properly :) [08:19] didrocks, hm [08:19] smspillaz, I can imagine :) [08:19] yeah. there are about a million code paths in compiz, very bug-prone [08:20] didrocks: also, french--; because they invented AZERTY keyboards [08:20] those things are hard to use [08:20] (this is on dbarth's netbook [08:22] didrocks: kamstrup: paste.ubuntu.com/535108 <- look familiar? [08:23] smspillaz: ugh, yeah it does [08:23] smspillaz: azerty keyboard is awesome :) [08:23] didrocks: lol [08:23] smspillaz: pull unity - i think didrocks committed a fix [08:23] smspillaz: yeah, do you use the trunk? [08:23] didrocks: lp:unity ? yes [08:23] smspillaz: what's the revision you have? [08:24] smspillaz: you on natty? [08:24] 614 fix it [08:24] well "fix"… [08:24] :) [08:24] 614 [08:24] kamstrup: yes, I'm on natty [08:24] smspillaz: did you reconfigure? [08:24] (I'm on rev 614 btw) [08:25] didrocks: pretty sure I did, but I can try a force clean, sec [08:26] morning people [08:27] hey sladen [08:27] (if this actually compiles then I will finally see if my glibmm stuff really does work) [08:29] didrocks: still doesn't compile, I'm on 614, there's no new revisions [08:29] meh, if I were to fix it manually, what should I stick in those files? [08:29] smspillaz: it shouldn't even try to compile those files [08:30] smspillaz: and it's working in natty (not compiling those file), not sure what you get locally [08:30] smspillaz: mehhh, compiz doesn't hang under gdb, tried 3 times… [08:30] didrocks: maybe I need to change the buildsystem [08:30] didrocks: hah! [08:30] smspillaz: can you give me your valac --version? Because it works fine here with valac from Maverick as well as with valac from Vala git master [08:30] smspillaz: autotools? (kidding) :) [08:31] kamstrup: 0.11.2 [08:31] didrocks: oh, as in, there is probably some lingering file in there [08:31] smspillaz: hmmm and I have Vala 0.11.2.20-376e2 here... [08:31] smspillaz: probably, like a remaining .c or whatever [08:32] smspillaz: let me try and checkout the released 0.11.2 version in git and see if it can reproduce [08:33] smspillaz: ok, meanwhile, did you create "projects" on git.compiz.org for the bailer and the detection plugin? [08:34] didrocks: git.compiz.org/users/smspillaz/bailer git.compiz.org/users/smspillaz/detectioon [08:35] smspillaz: even if it's uses/smspillaz, we take that as trunk, ok :) [08:35] smspillaz: so, that + a snapshot of compiz for A1 on Wednesday sounds good to you? [08:36] Hey folks. [08:36] evening TheMuso! [08:36] didrocks: sure. I just need to talk to iXce about getting it in /compiz [08:36] didrocks: BTW wrt to that session thing ... you know about how compizconfig allows you to have different settigns "profiles" and switch between them right? [08:37] didrocks: my idea was that we ship a wrapper script called "unity" which starts dbus services, launches compiz [08:37] smspillaz: not really [08:37] smspillaz: I saw the "profile" in ccsm, but not sure how they work [08:37] didrocks: it will automatically detect the session id and pass --profile="unityprof" so we can set all of the "unity" settings (including loading the unity plugin) [08:38] and then for gnomeclassic, we start up --profile="gnomeclassic" [08:38] smspillaz: and the user changes are stored in a different path locally? [08:38] didrocks: the user changes happen to the currently active profile [08:38] (in gconf or ini backend) [08:38] didrocks: and it's backend transparent, yes [08:38] ok [08:38] so I'll look into adding a --profile switch [08:39] so sounds good, but a wrapper script isn't good for performance… [08:39] usually we don't use switches in compiz, but the ccp thing is a special case [08:39] hum, I'm just worried about the wrapper TBH [08:39] didrocks: There's always going to be a script somewhere across the line (.xsession, etc) so even just put it in that one [08:40] and I'm pretty sure you can start things with arguments as part of a gnome-session component [08:40] smspillaz: not really, because it has a be launched by gnome-session [08:40] so, yeah, gnome-session component, I have to look at the code [08:40] (otherwise, how would we pass --replace to compiz and metacity?) [08:40] the issue is that if we do that, we are breaking many tools (as they change the gconf keys) [08:41] smspillaz: do you know about gconf layer, mandatory keys and sessions? [08:41] what tools? [08:41] didrocks: we'd only be changing stuff in /apps/compiz [08:41] smspillaz: ah, there is a gconf key for the profile? [08:42] didrocks: what do you mean by this? [08:42] smspillaz: can we change the profile chosen at start in /apps/compiz/ in gconf? [08:43] oh cool, someone got wayland working on an fb compositor [08:43] didrocks: no. the active profile is in .config/compiz/compizconfig/config.ini (iirc) [08:43] smspillaz: do you think it's feasable to get it into gconf? [08:44] smspillaz: the thing is, I think that a wrapper script will be rejected for that usage as we took so many times to kill them in lucid [08:44] didrocks: it could be done, but then we'd make a hard dependency on gconf [08:44] smspillaz: also, gnome doesn't really support sessions [08:44] * smspillaz doesn't want to do that [08:44] didrocks: are you sure it's impossible to pass switches to compiz when it starts up? [08:44] smspillaz: that's not the issue, let me take an example [08:45] so, gnome-session has a list of required component [08:45] ... if you're able to set DESKTOP_SESSION=unity, then you should be able to do compiz --replace --profile=foo & [08:45] one of those is the windowmanager [08:45] it's a gconf key stored in /desktop/gnome [08:45] ah right [08:45] until then, ok, I've introducted a hack to change the gconf system path depending on the session [08:46] so we can say "default for this session is compiz --replace foo" and "default for the other session compiz --replace bar" [08:46] the thing is [08:46] if the use change the windowmanager by default (it's their right), like in g-c-c [08:46] the key is changed [08:46] (so stored in ~/.gconf/…) [08:46] it overwrites both default, from whatever session [08:47] ah right [08:47] the workaround is to set it as a mandatory key [08:47] but that means, no way for the user to change their windowmanager [08:47] not sure it's acceptable :) [08:47] a mandatory key for the profile key in /apps/compiz would have been acceptable [08:48] hmm [08:48] is it possible for us to load a different .config per session? [08:48] transparently for compiz? [08:48] I'm pretty sure .config is some XDG evn var [08:48] smspillaz: right, but maybe we want different keys for compiz but not for ubuntuone, or shotwell, or whatever… [08:49] symlink them? [08:49] that's horrible :) [08:49] gah [08:50] didrocks: in that case, I am willing to change it slightly so that we don't use a switch --profile but maybe just a COMPIZ_PROFILE_NAME env var [08:50] is it possible to set that easily without impacting startup perf? [08:51] smspillaz: no problem to set that, we are aready doing that for the gconf hack [08:51] (in fact, COMPIZCONFIG_PROFILE_NAME is probably cleaner than --profile for a number of reasons) [08:51] the scripts in /etc/X11/Xsession.d/ are sourced and I'll add to an existing one [08:51] smspillaz: think just to fallback to default if it doesn't exists [08:52] smspillaz: that can happens if someone is creating a foo.desktop in /usr/share/xsessions/ [08:52] didrocks: yeah. The only problem I just thought of then is that if the user makes another profile they won't be able to switch to it [08:52] happen* [08:52] hum, you don't read .config first? [08:53] argh, but that would be the same for every sessions :} [08:53] we'll read .config first but obviously we want COMPIZ_PROFILE_NAME to override it [08:53] this session stuff is a headache since lucid! [08:53] I really think we should handle that in XDG to tell to apps "you should do that way", will be so much easier [08:54] didrocks: well, I'm trying to get this in upstream libcompizconfig [08:54] smspillaz: ok, but we should just find a way for the user to change their profile [08:54] hum… not easy :) [08:54] yeah [08:55] apart from an other settings "force" [08:55] like "don't take care about your sessions" [08:55] but again, that will impact all sessions [08:55] not ideal :/ [08:55] didrocks: let me think about this [08:56] didrocks: on the libunity vs valac compile failure.... [08:56] didrocks: do you think there's a usecase for the user changing their profile in the unity session? [08:57] didrocks: the problem is that the gio-2.0 vapi changed API between M and N [08:57] didrocks: and it's not trivial to make libunity compile on both afaics [08:57] if not, we'll set COMPIZCONFIG_PROFILE_NAME=foo there and for gnome-classic, not set anything (eg, load the default profile) [08:57] smspillaz: I think we can ignore that in the unity session as we want a well tested and known profiles, no headache. The gnomeclassic one, they can be… [08:58] kamstrup: you know for what platform you are developping, right? (hint: it begins with a N :)) [08:58] didrocks: ok then. so I'll add a COMPIZCONFIG_PROFILE_NAME to libcompizconfig [08:58] and then we specifiy the profile name [08:58] and load that directly [08:58] no need to "detect" session [08:58] smspillaz: nice! so, the profile will be the "default" in gnome-classic? [08:58] didrocks: yes [08:59] didrocks: Nintendo? [08:59] in gnome-unity it will be "Unity" [08:59] smspillaz: makes sense, making the changes in the xsessions scripts [08:59] kamstrup: hehe, nice try! [08:59] and we'll tweak the settings in the Unity Session to be more appropriate [08:59] kamstrup: oh, this "unity" game on wiiware? :) [08:59] there's a unity game on wiiware? [08:59] schweet! [08:59] smspillaz: no, just a joke :) [08:59] damn ;-) [08:59] I wonder if I should get a kinect [09:00] just for hax0ring [09:00] hook it up to libgeis XD [09:00] compiz with kinect support sounds interesting. [09:00] smspillaz: ok, once done, can we have a look about the profile thing? Not sure how to define a default profile telling "ok, create a unity profile with that plugins by default" (but hack the env variable first, will get that later) [09:00] hyperair: I once wrote a wiimote plugin for compiz too! [09:01] didrocks: we'll just ship it in the user's homedir skeleton by default [09:01] smspillaz: i know. i've never used it though. [09:01] didrocks: ok, everyone with slow CPUs can cry me a river then - I'm adding Vala to the jhbuild :-) [09:01] FUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU [09:01] kamstrup: hehe :) [09:01] lol [09:02] why, does vala take a long time to compile? [09:02] I hope it doesn't take as long as nux [09:02] hyperair: ok, it's not like a kernel, but does take some time - more than most components we use at least [09:02] kamstrup: FUUUUbuntu is what this is XD [09:02] smspillaz: it's in the same ballpark as nux [09:02] smspillaz: hum, shipping another homedir skeleton? but if we use the gconf backend rather? [09:02] kamstrup: hehe, ok [09:03] smspillaz: nux? [09:03] hyperair: it's a small layer that allows us to write unity on top of compiz [09:03] ah. [09:04] didrocks: we implement the profiles as ini files, yes [09:04] but you'll need the homedir skeleton anyways (to provide a .config/compiz/compizconfig to tell l-c-c to use the gconf backend [09:04] smspillaz: ok, and then, load that in gconf at startup I guess? [09:05] didrocks: yeah. If it's already loaded then it won't load again [09:05] smspillaz: ok, then, we will really need this "first time init script" for upgrading users [09:06] well it only happens once, like I said [09:06] so there's no need to put it in a "transition script" or anything [09:06] however, if you change sessions it will also change gconf keys around iirc [09:07] smspillaz: you still need the ini file to be shipped in the home directory, isn't it? [09:07] yes [09:07] smspillaz: so, what happens for users being on Natty today? they don't have it, hence the migration script to ship in ~ [09:07] smspillaz: apart from you look for the profile in a /usr/share/compiz if it doesn't exist [09:09] didrocks: we only install a Unity.profile [09:09] didrocks: the Default one is either created on first start, or we use the user's settings [09:10] smspillaz: right, but my question is rather: "where should be this Unity.profile?" can we ship in the system directory and that get copied (as the Default one) on first launch by compiz? [09:10] smspillaz: if we need to ship it in the user directory, that will be a fail as we have to handle people upgrading who doesn't have it [09:11] didrocks: it goes into .config/compiz/compizconfig [09:11] ah right [09:11] :) [09:11] maybe I should make it possible to load profiles from $PREFIX/share/compizconfig [09:11] smspillaz: I think compiz should first look at .config/compiz/compizconfig, and then, look in a known system dir if it doesn't find it [09:11] agreed, do you want some help on that? [09:11] that's what I was thinking [09:11] oh, I know how to do it [09:11] just have to ... do it [09:11] nice :) [09:12] preparing the profile meanwhile [09:12] kamstrup: where is this magical jhbuild thing of yuors [09:12] *yours [09:12] didrocks: here's a dare for you. Go into ccsm and tweak out all the settings to have lots of wobbly and fire and blur and save that as Unity.profile for A1 [09:12] just to make Jason explod [09:13] *explode [09:13] smspillaz: of course, and should I activate this "I love Jason" plugin too :) [09:14] I'll hack together a plugin which displays text on screen [09:15] <3 U JASON 4EVA [09:15] smspillaz: let me just push it to a public place [09:15] while there's plenty of fire, wobbly, water, blur, particles, cubes etc in the background [09:15] kamstrup: thx [09:15] smspillaz: can open a bug task and set to high :) [09:45] kamstrup: where is this link to your jhbuild? [09:55] smspillaz: looking at compiz core, there is no central point that is called when a plugin is unloaded, isn't it? (only this unload function which is inherited from plugin.h) [09:56] didrocks: no there isn't :( I'll need to make loaderLoadPlugin and loaderUnloadPlugin wrappable functions properly [09:57] so that we can so something like (in the future) python -> dl -> built-in [09:58] smspillaz: ok, nice to have in the future, not sure it's needed right now. So, it seems nothing more to add right now in the bailer/detection plugin, isn't it? [09:58] (for A1) [09:59] apart from now hacking gnome-session to add required components on the fly [09:59] didrocks: yeah. I think getting loaderLoadPlugin and loaderUnloadPlugin wrappable should be an easy task [09:59] it basically is now, except in a more "manual" way [10:00] smspillaz: so that, when a "shell" plugin unload, we fallback to another shell, sounds the best way to deal with it (but we can deal with it manually in unity now) [10:00] didrocks: yeah, just hardcode it for now [10:00] didrocks: you should be able to push to both the bailer and detection plugins [10:01] smspillaz: done already if you didn't notice :) [10:01] ah right ;-) [10:01] smspillaz: I've removed the env var as well as we will deal with the profile [10:01] ok, so now gnome-session hacking :) [10:01] didrocks: we don't have CIA.vc running on the userrepos so I didn't get a text message about it XD [10:02] smspillaz: well, make sense to avoid spamming… [10:02] heh [10:02] you should have seen my phone bill when I pushed about 500+ committs to group about 3 weeks ago [10:03] smspillaz: oh, you pay depending the bits you are pushing? [10:03] oh, just for all the text messages I receieved XD [10:03] I forgot to turn notifications off and my phone was on silent [10:04] go back the next day and I have 500 new messages [10:04] ahah :) [10:05] njpatel: dude, you won't have time to work on the file:///*.desktop for the launcher this week, I can handle it along with the migration script if needed? [10:07] you can, though I do need to work on that code for other things this week, so i'll probably add the file:// stuff tomorrow [10:07] but i won't be doing the migration stuff [10:07] njpatel: oh ok, so updating the migration stuff only then :) [10:07] also changing the defaults [10:08] njpatel: when did you need the decorations stuff done btw? [10:09] smspillaz: hum, it's normal that you couldn't build the last version, Jason --overwrite my branch [10:09] grrr :) [10:10] so rev 614 isn't mine [10:10] * didrocks rebase and push [10:10] didrocks: ahahahahahaha [10:10] smspillaz: so, rev 615 should build :) [10:11] ok :p [10:51] njpatel: assigning that one to jay? Unity won't be in A1 otherwise :) https://bugs.launchpad.net/unity/+bug/678460 [10:51] Launchpad bug 678460 in nux (Ubuntu) "don't ship .bmp files but rather .png (affected: 1, heat: 6)" [Critical,Triaged] [10:53] didrocks, urgh, yes, of course [10:54] didrocks, also, I don't think he can ship those files [10:54] njpatel: so, using system font rather? [10:54] why does natty insist that I am using firefox as my default browser? [10:54] njpatel: yeah, it's quite aggressive about it :/ [10:54] didrocks, no, this is something else [10:54] didrocks, will figure it out with jay [10:54] njpatel: ok, nice :) [10:54] thanks [10:55] * njpatel doesn't want to use firefox [10:55] njpatel: the thing is, there is still the same bug for me with a very slow firefox on nvidia with launchpad… [10:55] right [10:55] also, their bastardisation of the current Gtk theme hurts my eyes [10:56] didrocks, natty using firefox 4 yet? speed improvements in that have made a big difference to me [10:56] at least chromium is upfront in that they aren't going to respect it [10:56] gord, FF 4.0 beta 7 [10:56] must be a fun cairo problem then [10:57] gord: not really on firefox vs launchpad for me, still the same bug where launchpad guys says "not our fault if we use repetition in images" and where Mozilla tells "we don't support that" [10:57] if your website is slow in one of the worlds most popular browsers, it is your fault ;) [10:58] njpatel, because they changed how the handlers are working [10:58] njpatel, re why does natty insist that I am using firefox as my default browser? [10:58] njpatel, you need to claim the handler/http type in the .desktop or something [10:58] njpatel, check with chrisccoulson if you want for the specifics, he fixed firefox for it [10:59] chrisccoulson, ^ (didn't notice you were here) [11:01] njpatel, i think the only way to set your default browser currently is by hand editing mimeapps.list [11:01] dbarth: it's already known where the g_main_loop is going to impact plugins [11:02] dbarth: basically 1) can't re-set timers while running (glib regression) [11:02] 2) the filewatch stuff needs to be ported [11:02] njpatel, you need to edit ~/.local/share/applications/mimeapps.list and add something like x-scheme-handler/http=chromium-browser.desktop;firefox.desktop [11:02] (and the same also for https) [11:02] chrisccoulson, ah, thanks [11:03] njpatel, this will be fixed in firefox once mozilla bug 611953 has landed, but i don't know if anybody is working on the chromium changes [11:03] Mozilla bug 611953 in Shell Integration "GNOME 3.0 readiness" [Normal,New] http://bugzilla.mozilla.org/show_bug.cgi?id=611953 [11:03] interesting [11:04] i guess i should reserve some time to fix chromium too [11:12] chrisccoulson, don't bother, fta will likely do it [11:16] njpatel, [11:16] http://seilo.geekyogre.com/uploads/2010/11/Screenshot.png [11:16] :) [11:16] seiflotfy_, niiice :D [11:17] i even have a video showing that it works [11:29] seiflotfy_, pretty! i wonder if we can do something about those icons though, maybe force a rounded edge [11:31] gord, good idea [11:36] njpatel: yeah, rounded edges would be nice. That could be a new renderer [11:37] kamstrup, yep, it definitely will be [11:37] the plan is to make the entire thing look nicer and add a few more renderers at the same time [11:38] njpatel: I assume you are the scoundrel that removed all my unit tests for UnityAppInfoManager? [11:38] kamstrup, yes, yes, don't worry, they will be restored [11:39] njpatel: yeah, because I'm just updating Unity.IO and Unity.AppInfoManager to conform to the latest breakage in the GIO VAPI [11:39] ah, right [11:40] njpatel: I had to break libunity API for that, and it would be nice to assert that I didn't break too much :-) [11:41] njpatel, must i remind you of http://twitter.com/#!/njpatel/status/19843856935 [11:43] kamstrup, will try and have that by EOF, before releasing for A1. I'm currently trying to figure out why unity is so crashing on maverick [11:44] mavercik? I mean natty [11:44] seiflotfy_, yeah, but after that we found one bug of kamstrup, therefore he's just as crap as the rest of us!!!! [11:44] w000000000000000000t [11:44] how dare you [11:45] for what it is worth, it is quite crashing on maverick too ;) [11:46] :) [11:49] any specifc apps that cause the crash would be helpful :) [11:50] knowing which specific... * [11:50] wow, shadows are broken [11:51] in my case, its firefox and gwibber that tend to do it. the first far more than the second. [12:00] Would the following bug be suitable for a papercut, it is basic functionality of Launchpad, not the desktop: [12:00] https://bugs.launchpad.net/bugs/68277 [12:00] Launchpad bug 68277 in Launchpad Bugs ""newest first" doesn't sort bugs correctly (affected: 1, heat: 0)" [Undecided,Confirmed] [12:11] so who had the fun idea of doing infinite recursion in unity? [12:11] hmm, these bamf crashes are weird [12:12] Depends, where does it happen? if it's panel then probably me [12:12] njpatel: i'm not really sure because it's hard to get a stack trace... [12:15] njpatel: here http://paste.ubuntu.com/535171/ [12:16] mother of god [12:16] at least it's not me [12:16] * njpatel tries to decipher that === MacSlow is now known as MacSlow|lunch [12:26] hi there [12:28] njpatel: the nice thing about c++ is that it gives you totally easy to read stack traces ;-) [12:29] njpatel: I think it must be some compiz related change that caused this since the changes in unity since last are minimal [12:29] njpatel: c++filt. learn it. live it. love it. [12:30] kamstrup: hm? [12:30] smspillaz: what's your take on here http://paste.ubuntu.com/535171/ ? [12:30] kamstrup, does it happen every start? [12:30] njpatel, smspillaz: happens whenever I start 'compiz ccp' [12:30] sigc failing at life as usual [12:31] let me have a look at the code [12:31] smspillaz, what does ccp actuall mean/do? I don't ever start compiz with it [12:31] njpatel: compiz configuration plugin [12:31] i'm assuming that's default? [12:31] njpatel: it's basically left behind from the whole compiz-fusion/compiz thign when david reveman wouldn't accept our patches for ccsm and like so we wrote our own configuration thingo [12:31] ah [12:31] njpatel: but yes, it is the default, no, it can't go into core for various reasons [12:32] sure [12:32] :p [12:33] we also have a small ini plugin that we ship with core too which is a bit lighter than compizconfig, but there's no graphical tool for it [12:34] if we can pull glib into trunk, can we just have a gsetttings plugin and be done with it? [12:34] njpatel: it will be much easier to write a gsettings backend for libcompizconfig [12:34] seems like it would solve your problems (dconf or keyfile backend), and you don't need to maintain it [12:34] cool [12:34] in fact, we can do that right now [12:34] ... I just need to finish my mountain of other stuff too [12:35] also, I don't want to pull glib into trunk just yet because there is some mainloop stuff that is NI [12:35] (eg filewatches [12:35] right, no rush :) [12:35] njpatel: it seems we won't take the gsettings backend this cycle if we don't upgrade g-s-d, which is more than probable [12:37] cool === smorar__ is now known as smorar [12:37] njpatel: is it a cool like a monkey island: "nice"? :) [12:38] :) [12:41] kamstrup: hmm, sigc::mem_fun (this, &Launcher::RecvMouseDown) should basically not compile if you ask it to do something unsafe [12:41]