[00:09] <racarr> RAOF: YAy not sick welcome back
[00:09] <RAOF> What can I do for you?
[00:10] <racarr> I was just wondering if you had any thoughts on cursor name being a string v. an enum
[00:10] <racarr> daniel suggests an enum...it seems reasonable as most toolkits suggest
[00:10] <racarr> an enum
[00:10] <racarr> is there any reason to make it a string? weird cursor names, etc?I just remember reading something along time ago about firefox requesting a cursor calle like hfasu8u398u32xxx7 or something
[00:11] <racarr> so you had to have that in your xcursor theme
[00:11] <racarr> lol
[00:11] <RAOF> :)
[00:12] <RAOF> So, one reason to make it a string would be so that we don't have to bake in every weird and wonderful cursor.
[00:13] <RAOF> racarr: Is this in response to a particular merge request? I should probably read in context.
[00:15] <racarr> RAOF: Still cursor-spike-phase-1 ;)
[00:16] <racarr> The others are ready though lol (well almost...still cleaning up one test)
[00:16] <racarr> that is the one reason to make it a string which is my thought too aha...I mean in the toolkit you still have
[00:17] <racarr> to have a big switch on the toolkit enum types to translate it to mir types
[00:17] <racarr> so might as well use a string...?
[00:19] <RAOF> I think I prefer strings, yes.
[00:19] <RAOF> With #defines for MIR_CURSOR_CROSSHAIR, etc.
[00:27] <racarr> mm yeah defines would be good I guess
[00:28]  * RAOF reviews in ernest.
[00:35] <racarr> RAOF: Thank you :) ill be back in an hour or two so can iterate if you have thoughts.
[00:36] <racarr> this https://www.bitwig.com/en/home/recent-news.html got released today so I am going to go play for a while...
[00:36] <racarr> (Software?! For my operating system?!)
[00:36] <RAOF> Funky!
[00:36] <RAOF> :)
[07:06] <mlankhorst> morning
[16:36] <alan_g> alf__: do you have time for: https://code.launchpad.net/~alan-griffiths/mir/remove-one-of-the-redundant-surface-factories/+merge/212923?
[16:36] <alf__> alan_g: looking
[16:37] <alan_g> thanks
[16:46] <alf__> greyback: if you want to test you will need both lp:~afrantzis/mir/android-gl-config and lp:~afrantzis/mir/nested-gl-config for nested
[16:46] <alf__> greyback: otherwise wait until they reach devel :)
[16:47] <greyback> alf__: noted, thank you
[18:37] <jhodapp> Anybody know why running a QtTest on a target device results in it hanging trying to connect to Mir? I have this backtrace: http://pastebin.ubuntu.com/7169856/
[20:36] <kgunn> bschaefer: i tried but i got a blocks-demo crash file
[20:40] <kgunn> bschaefer: https://drive.google.com/a/canonical.com/file/d/0B4GvOYxwuvpFeHdsQi04Zk5nR0E/edit?usp=sharing