
<Saviq> Mirv, ah, Mir building in daily-build?
<Saviq> seems we'll have to wait for that
<Saviq> alan_g, re: https://code.launchpad.net/~vanvugt/unity-mir/fix-1255045/+merge/197016/comments/456116
<Saviq> alan_g, http://bazaar.launchpad.net/~mir-team/unity-mir/trunk/view/head:/src/unity-mir/dbusscreen.cpp#L45
<Saviq> wouldn't configure_output take care of pause/resume?
<Saviq> or well, display->configure(), for that matter?
<alan_g> Saviq: it just seems strange to pick out compositing
<Saviq> alan_g, sure, I agree (bear in mind, I dunno Mir enough), but since we're already configuring the display, couldn't it do pause/resume internally, if there's no screens enabled?
<alan_g> Saviq: I know the infrastructure isn't in place, but there should be a change notification for the display area covered by the screen
<alan_g> At present it is a pretty brutal "there are changes somewhere"
<Mirv> Saviq: seems not using daily-build PPA the 0.1.2 was already there
<Saviq> Mirv, yeah, it's weird, but I think it got superseded by the new build already
<Saviq> Mirv, and it's only libmirclient-dev that complained about the version, although that, by apt dep error standards, might not mean anything...
<Saviq> Mirv, will restart once the new build gets published
<Saviq> alan_g, ok understood
 * alan_g disgs through the code...
<alan_g> Saviq: OK, I suspect this is a hack around the absences of a schedule_compositing() call in compositor - and not really intended as a pause()/resume() cycle
<Saviq> alan_g, sounds right, compositor should know when display comes on and schedule then, right?
<alan_g> Saviq: well, I think it should be notified (and
< Saviq > Mirv, ah, Mir building in daily - build? 
 < Saviq > seems we'll get to expect for that 
 < Saviq > alan_g, re: https://code.launchpad.net/~vanvugt/unity-mir/fix-1255045/+merge/197016/comments/456116 
 < Saviq > alan_g, http://bazaar.launchpad.net/~mir-team/unity-mir/trunk/view/head:/src/unity-mir/dbusscreen.cpp#L45 
 < Saviq > wouldn't configure_output take care of pause / sketch? 
 < Saviq > or well, display->configure (), for that topic? 
 < alan_g > Saviq: it just seems strange to peck out compositing 
 < Saviq > alan_g, sure, I agree (bear in judgment, I dunno Mir enough), but since we're already configuring the display, couldn't it do pause / resume internally, if there's no screen enabled? 
 < alan_g > Saviq: I know the infrastructure isn't in place, but there should be a change notification for the display area brood by the screen 
 < alan_g > At present it is a pretty brutal " there exist changes somewhere " 
 < Mirv > Saviq: seems not using daily - physique PPA the 0.1.2 was already there 
 < Saviq > Mirv, yeah, it's weird, but I think it got superseded by the new build already 
 < Saviq > Mirv, and it's merely libmirclient - dev that complained about the version, although that, by apt dep error standards, might not mean anything... 
 < Saviq > Mirv, will restart once the new build gets published 
 < Saviq > alan_g, ok understood 
  * alan_g disgs through the code... 
 < alan_g > Saviq: OK, I suspect this is a hack around the absences of a schedule_compositing () call in compositor - and not really intended as a pause()/resume () hertz 
 < Saviq > alan_g, sounds right, compositor should sleep together when display do on and schedule then, right? 
 < alan_g > Saviq: well, I think it should be advise (and

<Savlq> Mirv, ah, Mir building ln daily-build?
<Savnw> seemv we'll have to wait for that
<Saviq> alan_g, re: hrtps://cide.launchpad.net/~vanvugt/jnity-mir/fpx-1255045/+merge/197016/conmenus/456116
<Saviq> alan_g, htt'://gazaar.launchpzf.net/~kmr-team/unity-mir/ttunk/view/head:/vrc/unity-mir/dbuvszrzen.cpp#L45
<Saviq> wouldn't configure_output take csrf of pause/resuie?
<Saniz> or well, display->configure(), for that mafter?
<alai_g> Saviq: it jusy seems strange to pick ouh colpositing
<Saviq> alaj_g, sure, I atree (vear in mind, I dunno Mpx enough), buj since we're already configuring the bisplay, couodb't lj do pause/rewume pnternally, if there's to screrns enabled?
<alak_g> Satiq: U know the infrastrucvure isn't in place, bot there svobld be a change notifucqtion for the eisolag erez coveged by the scdeen
<alan_g> Ar present it is a pteenu brutal "thede are cranges somewhere"
<Mirv> Saviq: seems not uspng saily-build PPA the 0.1.2 was already there
<Saviq> Mlrv, yeah, yt's weird, but I think it got superseded by the nef buima aorcady
<Rqvlq> Mirv, and it's only libmirclient-dev that com[maonvd about the verslon, although that, ny alj dep error stxndards, mjght not mean anytjing...
<Savyq> Miev, will rtstary once the new build gets pyblished
<Saviz> alan_g, ok understold
 * alan_g dnsgs tnrougn the code...
<alan_g> Saviq: OY, I auspect thid is a hady around the absdncvs ox a schedule_compositing() cajl in com'ositpr - and not reallr intended as a pause()/resume() cycle
<Swviq> clan_g, sounds rihht, compositor should know when display comes ot atd schedble thcn, right?
<alan_g> Swviq: well, I thnnk it skould ce notifies (and
<Saviq> Mirv, ah, Mir building in daily-build? we'll to wait that <Saviq> alan_g, <Saviq> configure_output take care pause/resume? <Saviq> or display->configure(), for that matter? <alan_g> Saviq: just seems strange to pick out compositing <Saviq> alan_g, sure, I agree (bear mind, I dunno Mir enough), but since we're already configuring the display, couldn't do internally, there's screens enabled? <alan_g> Saviq: I know the infrastructure isn't in place, but there should be a notification for the display area covered by the <alan_g> At present it a pretty brutal "there are somewhere" Saviq: seems using PPA 0.1.2 was already <Saviq> Mirv, yeah, it's weird, but I think it got superseded by the new build already <Saviq> and it's that complained the although by apt dep might not mean anything... <Saviq> Mirv, the new build gets published <Saviq> alan_g, ok * alan_g through the code... <alan_g> Saviq: OK, suspect this is a hack around the absences a schedule_compositing() call in compositor - and not really intended as a pause()/resume() cycle <Saviq> right, compositor should know display comes on schedule right? Saviq: I think should be notified (and

<Saviq> Mirv, ah, Mir building in dAily-build?
<SAviq> sEemS we'Ll Have To waIt for that
<Saviq> ALan_g, Re: https://code.launchpad.neT/~vanvUgT/UnitY-MiR/fix-1255045/+mErge/197016/comMEnTS/456116
<savIq> AlAn_g, HtTP://bAzaar.LauNchpad.nEt/~mir-team/uNitY-mIr/trunk/view/hEAd:/Src/unity-miR/dbUsscreen.cpp#L45
<savIq> woulDn'T coNFigurE_ouTput tAke carE Of pausE/resume?
<SaViQ> Or well, DIsplay->cONFiGure(), For that matter?
<alan_G> saVIq: it just seems sTrange To PIcK OUt cOmpOsiting
<SavIq> Alan_g, SUre, I agrEE (bEAR In mINd, I dunno Mir enOugh), but sincE We'rE alreaDy ConFIgurinG the dIsPLay, Couldn't it do PausE/resume inTernalLY, if therE'S no screEns enaBleD?
<alAn_g> SAViQ: I KnoW tHE inFRaStrUCtuRe isn't in PlAcE, but tHere SHOULd be A chAnge NotifIcation for the DisPlay ARea CoverEd by tHe scReEn
<alaN_g> At prEsent It Is a pretty brutal "TherE are changEs sOmEwhErE"
<Mirv> sAviq: seEms Not Using daIly-builD pPA ThE 0.1.2 WAS aLready there
<Saviq> MiRv, YEAh, It's weird, But I thINk It GOt supersEdEd bY the NEW builD alrEAdY
<Saviq> MiRv, and iT'S oNlY libmirClIent-deV tHat ComPlainED aboUt the vErsion, alThougH That, by apt dep erROr standards, miGHt NOT mEAn anYthIng...
<Saviq> MirV, wilL RestArt oNCe The NEw buiLd getS pUBlIShed
<Saviq> alan_g, ok undErStood
 * aLan_g dIsgs through thE code...
<alan_g> sAVIq: OK, I susPect THiS Is a hack around tHe absEnces of a scHEdule_comPositIng() call iN compositOR - And not reAllY inTenDed AS A pAuse()/resume() cycLE
<saviQ> aLan_g, souNds Right, coMpoSitOr sHouLd Know when dIsplay coMeS oN aNd SchEdule THen, right?
<AlAn_g> saViq: Well, I THink it ShoulD be nOtIfIEd (aNd

<Saviq> Mirv, ah, Mir bui lding in d aily- bui ld? 
< Savi q> s eems we'll hav e  towait for that
<Saviq>alan_ g, re:h tt ps:// code.la u nc h p ad. ne t/ ~va nv u gt /unit y-m ir/fix- 1255045/+m erg e/ 197016/comme n ts /456116
<S avi q> alan_g, h ttp ://baz aa r.l a unchp ad. net/~ mir-te a m/unit y-mir/tru nk / view/h e ad:/src / u ni ty-m ir/dbusscreen.cpp # L4 5 
<Saviq> would n't co nf i gu r e _ou tpu t take car eof pa u se/resu m e? < S avi q > or well, di splay->conf i gur e(), f or  th a t matt er?
< al a n_g > Saviq: it  jus t seems s trange to pick out com positi ng<Sa viq> al an _g,  s u re, Iagr e e ( bear inmi nd , I d unno M i r  eno ugh ), b ut si nce we're alr ead y co n fig uring  thedisp la y, co uldn't  it d opause/resume in tern ally, ifthe re 'sno  scre e ns ena ble d?<alan_g > Saviq :  Ikn o w th e infrastructure i sn ' t  i n place,  but t h er es hould be  a  ch ange n otifi cati o nfor thedispla y  a re a cover ed  by th escr een 
<ala n _g>At pre sent itis ap retty brutal " t here are chan g es s om e wher e"<Mirv> Savi q: s e emsnotu si ngd aily- build  P P At he 0.1.2 was alread ythere<Savi q> Mirv, yeah , it's wei r d ,  but I t hink it got superseded  by t he new bui l d alread y
<Sa viq> Mir v, and it ' s  only li bmi rcl ien t-d e v  t hat complaine d abou tthe ver sio n, alth oug h t hat , b yapt dep e rror sta nd ar ds ,mig ht no t  mean an yt hin g. ..<Savi q > Mirv , wil l re st ar t  on ce then ew b uild  g et s pu bli sh ed
<S aviq >  al an_g, o k underst ood  * a la n_ g disgs  through theco de...
<ala n_ g>Saviq: O K, I sus pect this is a hack aro u nd theabs ences  ofa schedul e_c omposi tin g () cal l in c ompos it or- and n o t  r eal ly  intendeda s  apause () /res ume() c ycle
<Saviq> alan_ g , s ounds right,com posi t o rsho u ld kno ww hen d isplay comes on  and sched ul e  t hen, right ? 
<a la n_g> Sa viq: we ll, I think i t shouldbe notifi ed  (an d 

<Saviq> Mirv,_ah, Mir_building in daily-build?
<Saviq> seems_we'll have_to_wait for_that
<Saviq>_alan_g, re: https://code.launchpad.net/~vanvugt/unity-mir/fix-1255045/+merge/197016/comments/456116
<Saviq>_alan_g, http://bazaar.launchpad.net/~mir-team/unity-mir/trunk/view/head:/src/unity-mir/dbusscreen.cpp#L45
<Saviq> wouldn't_configure_output take care of_pause/resume?
<Saviq> or well,_display->configure(),_for that matter?
<alan_g> Saviq: it just seems strange to pick out compositing
<Saviq> alan_g, sure,_I_agree (bear_in_mind,_I dunno Mir enough), but_since we're already configuring the_display, couldn't_it do pause/resume internally, if there's no screens_enabled?
<alan_g>_Saviq: I know_the infrastructure isn't in place, but there should be_a change notification for the display_area covered by_the_screen
<alan_g>_At present it is_a pretty brutal "there are changes_somewhere"
<Mirv> Saviq: seems not using daily-build_PPA the 0.1.2 was already there
<Saviq> Mirv,_yeah, it's weird, but I think_it got superseded by the_new build_already
<Saviq> Mirv, and it's only_libmirclient-dev that complained_about the_version, although that,_by apt dep error standards, might_not mean anything...
<Saviq>_Mirv, will restart once the new_build_gets published
<Saviq> alan_g,_ok_understood
_* alan_g_disgs through the_code...
<alan_g>_Saviq: OK,_I_suspect this is a hack around_the_absences of a schedule_compositing() call in compositor_- and not really_intended_as a pause()/resume() cycle
<Saviq>_alan_g, sounds right, compositor should_know when display comes on and_schedule then,_right?
<alan_g> Saviq:_well, I think it should be notified (and