/srv/irclogs.ubuntu.com/2014/12/03/#ubuntu-mir.txt

=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
mlankhorsthuh10:01
mlankhorstwhy would unity8 give me a surface that has slightly more width than the screen?10:02
mlankhorstNew size: 1366x74210:02
mlankhorstwhile the screen is 1360x76810:02
mlankhorstoh no, it's 1366 after all, wonder why it says 1360 then..10:03
greybackmlankhorst: a unity8 bug most likely. I'm aware of a bug where the surface height you end up with is 4 pixels too tall (for non-fullscreen surface)10:03
mlankhorstoh no, it might be some thing I need to workaround in xmir, bug in the resolution stuff10:04
duflu_mlankhorst: Interestingly Xorg also reports physical dimensions (xrandr) completely wrong. Mir does not10:33
* duflu_ wanders off10:33
mlankhorstshrug :P10:34
mlankhorstI'm fighting with Xmir atm, getting some nice interactions where u8 resizes my newly created Xmir window and I currently don't handle that. I need to detect the case where Xmir runs in a window and handle xrandr differently there..10:36
mlankhorstcan I detect the window is created with a different somehow? the resize event seems to be delayed..10:58
greybackmlankhorst: unity8's window sizing is a bit flawed right now. When clients requests surface, it is given fullscreen surface. Then when first frame is swapped, does unity8 resize surface to what is wants11:00
greybackso you always get a resize event shortly after surface creation11:00
mlankhorstok, that would explain things..11:00
greybackknown issue, I have code to fix it, I need to resurrect it and land it11:00
mlankhorstthat would really help me. :P11:01
greybackmlankhorst: ok, let me do that today.11:01
alan_ggreyback: are you now happy with my qtmir changes? (I tracked down my problems to PEBCAK)11:03
greybackalan_g: I am, just need to check one thing and then I can TA the new-migrate. Will then move onto the refactor, but from my initial look there was nothing controversial11:04
alan_ggreyback: great11:05
mlankhorstgreyback: but that could open another bug, until I call mir_surface_set_event_handler I can't process messages from the surface11:09
mlankhorstso if you fix it will it be race-free?11:09
greybackalan_g: can you answer that? ^^11:10
greybackmlankhorst: my understanding is when client calls mir_connection_create_surface with certain geometry defined in MirSurfaceParamters, the MirSurface returned should be checked again by the client to see the geometry it is given - as they may not be the same.11:13
mlankhorstyeah, unfortunately I don't see a call to do so..11:13
greybackmlankhorst: mir_surface_get_parameters should do it11:15
alan_gmlankhorst: what race are you concerned with?11:16
alan_gthe size of the surface you have is available locally (as greyback says) and needs to be checked11:18
mlankhorstwhat call gives me the size then?11:18
mlankhorstoh right, the MirGraphicsRegion11:20
mlankhorstbut that only works for cpu rendering, not gl11:23
mlankhorstoh nm, found it11:26
=== dandrader is now known as dandrader|afk
greybackalan_g: all approved, many thanks12:54
=== dandrader|afk is now known as dandrader
alan_ggreyback: thank you.12:57
=== alan_g is now known as alan_g|lunch
=== Trevinho_ is now known as Trevinho
=== alan_g|lunch is now known as alan_g
=== chihchun_afk is now known as chihchun
=== alan_g is now known as alan_g|tea
=== alan_g|tea is now known as alan_g
=== dandrader is now known as dandrader|lunch
=== dandrader|lunch is now known as dandrader
=== chihchun is now known as chihchun_afk
rsalvetikgunn: kdub: hey, have one question about mir and the input system and events, who knows more about that?20:56
rsalvetibasically I want to understand what is the flow for the evdev events we get on our devices20:56
kgunnrsalveti: racarr and anpok20:56
rsalvetiI know the shell is the one handling all the input, probably via mir20:56
kdubprobably racarr in this timezone20:56
rsalveticool, thanks20:57
rsalvetihm, no racarr around20:57
kgunnrsalveti: he's just gone for lunch...20:57
rsalveticool, will ping him later then, thanks!20:57

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!