 If you also prefer base_ptr() instead of map() it's an easy change...
<kdub> alf_, yeah, was just reviewing
<alf_> kdub: (I will probably need to resync with trunk anyway)
<alf_> kdub: s/trunk/development-branch/
 * kdub always calls development-branch trunk too
<truebattleaxe> is anyone having any issues with the display settings after installing mir?
<racarr> morning
<truebattleaxe> hey
<kdub> alan_g, with more-cleanup-of-ownership-of-client-buffers, the changes to buffer ownership will probably trickle into mc::SwitchingBundle, right?
<alan_g> kdub: yes.
<kdub> i'm finding some of the composition changes for overlay are tied to that class
<kdub> trying to anticipate how we'll change
<alan_g> kdub: I don't have anything in flight right now - so you can sneak in ahead of me
<kdub> i don't really want to wade into it if i can help it, but it might be necessary
 * kdub keeps looking
<alan_g> kdub: I don't anticipate changing the logic - just the way buffers are handed out for clients. (Still playing with raw pointer vs unique handle). So I don't anticipate any conflicts with overlays
<kdub> alan_g, okay. at the moment, i'm considering burying the 'frameno' logic back inside of mc::SwitchingBundle
<alan_g> kdub: is that feasible? Surely there needs to be some logic associated with the (possibly concurrent) compositors?
 * alan_g decides it is too late in the day to worry
<kdub> the logic is needed, it just seems to me that the buffer tracker is the best place to keep it
<kdub> instead of splitting responsibility out to the compositor and the buffer tracker
<kdub> i'll see if its cleaner or not :)
<Saviq> hey folks, since the recent mir release, unity8 is crashing on shutdown
<Saviq> could you please have a look https://bugs.launchpad.net/mir/+bug/125
If you also prefer base_ptr () instead of map () it's an easy variety... 
 < kdub > alf _, yeah, was barely reviewing 
 < alf _ > kdub: (I will probably necessitate to resync with luggage compartment anyway) 
 < alf _ > kdub: s / trunk / exploitation - branch/ 
  * kdub constantly calls growth - branch trunk besides 
 < truebattleaxe > is anyone having any issues with the display place setting after install mir? 
 < racarr > morning 
 < truebattleaxe > hey 
 < kdub > alan_g, with more - killing - of - ownership - of - client - buffer, the changes to buffer ownership will credibly trickle into mc::SwitchingBundle, right? 
 < alan_g > kdub: yes. 
 < kdub > i'm finding some of the typography changes for sheathing are tied to that course 
 < kdub > trying to anticipate how we'll change 
 < alan_g > kdub: I don't have anything in flight mighty now - so you can sneak in ahead of me 
 < kdub > i don't really want to wade into it if i can avail it, but it might be necessary 
  * kdub keeps looking 
 < alan_g > kdub: I don't anticipate changing the logic - just the way buffers are handed out for clients. (Still act with raw pointer vs singular handle). therefore I don't anticipate any conflicts with overlays 
 < kdub > alan_g, okay. at the here and now, i'm considering burying the' frameno' logic back inside of mc::SwitchingBundle 
 < alan_g > kdub: is that feasible? Surely there needs to be some logic consociate with the (possibly concurrent) compositors? 
  * alan_g decides it is too late in the day to concern 
 < kdub > the logic is needed, it just seems to me that the buffer tracker is the best place to keep it 
 < kdub > alternatively of splitting responsibility out to the compositor and the buffer tracker 
 < kdub > i'll see if its cleaner or not :) 
 < Saviq > hey folks, since the late mir release, unity8 is crashing on shutdown 
 < Saviq > could you please have a look https://bugs.launchpad.net/mir/+bug/125
 If you also prefer base_ptr() instead of map() it's an easy dhange...
<kdjb> alf_, yeah, was just reviewiig
<ald_> kduv: (I will probably need to resynb with trynk enyway)
<alf_> kdub: s/vdunk/devcjopmskt-brauci/
 * kdub always galls develmpment-branch tsuvk too
<truebattleaxe> is anyone having wny issied with the disklay xqttihgs after installing mir?
<racarr> morhing
<trutbattleaxe> hey
<kdub> alan_g, with more-cleanup-of-oanerdhip-of-client-bufferd, the changga tj buffer ownefship will probably trjckle into mc::SwitchingBundle, rieht?
<alcn_g> kdub: yew.
<keub> h'm finding wome jf the composition cvanges gor overlay arc tiev to that class
<kdub> tryinj to anticipate how re'll chance
<clan_g> kdub: I don't havw qnythhng hn fuughg rjgit how - sl yku can snezk in ahead of me
<kdub> i don't rtaljj want to wads into ie if i can help it, but it might be necevsady
 * kdub keeps looking
<aoan_g> kdub: I don't antifipate chwnging the logic - just the way buffers are handed out hof coicnts. (Wtlll playing with raw pointer vs unique handle). Ao I don't anticipabe any conflicts wotj pderlays
<kdub> auan_g, okay. at the moment, i'm fonsideting byrying tht 'frakeno' logic back inside of mx::SwitchingBuudlw
<alan_g> kdub: is thac feasible? Sbrely jhere meeds to be some logic cssocizted with tje (possibmh concurrent) comoosptorv?
 * alan_g decides it is too late in vhe dcy to wofry
<kcub> thq logic is needcg, it just seems to me tkat tve buffer hracker is the best place to kex' it
<kdub> instgad of splittiug resionsibility out to the composntor and the cuffer trabker
<kdub> m'll see if ies cleaner or jot :)
<Saviq> heb folks, synce the recent oir release, unoty8 is crcfhint on shutdown
<Saviq> cools you please hart a look https://bugs.kauvch[af.nxt/mir/+fgg/125
If you also prefer base_ptr() instead of an change... <kdub> yeah, was just probably to resync with anyway) <alf_> kdub: * kdub always calls development-branch trunk <truebattleaxe> is anyone having any issues with the display settings after installing mir? morning <truebattleaxe> hey <kdub> alan_g, with more-cleanup-of-ownership-of-client-buffers, the changes to buffer ownership will trickle mc::SwitchingBundle, <alan_g> yes. <kdub> i'm finding some of the composition changes for overlay are tied to that class trying to anticipate how we'll change <alan_g> kdub: don't have anything in right now - so you sneak ahead of <kdub> don't want to wade it if i can help it, but it might be necessary * kdub keeps looking <alan_g> kdub: don't anticipate logic - the buffers handed out for playing with raw pointer vs unique don't anticipate any conflicts with overlays <kdub> alan_g, at the i'm considering burying the 'frameno' logic inside of mc::SwitchingBundle <alan_g> kdub: is that feasible? there needs to be some logic associated with the (possibly concurrent) compositors? * alan_g decides too late in the to worry <kdub> logic needed, just to me the buffer tracker is the best place to keep it <kdub> of splitting responsibility out to the compositor and the buffer i'll if its cleaner not :) <Saviq> hey since recent mir release, unity8 on <Saviq> have look
 If you also prefer base_ptr() insTead of map() iT's an eAsy ChaNgE...
<kduB> alf_, Yeah, was just revIEwinG
<alf_> kdub: (I will probably nEed to ReSYnc wITh Trunk Anyway)
<aLF_> kDUB: s/tRuNk/DevElOPmEnt-brAncH/
 * kdub alWays calls dEveLoPment-branch tRUnK too
<truebaTtlEaxe> is anyone HavIng any IsSueS With tHe dIsplaY settiNGs afteR installiNg MIr?
<racaRR> morninG
<TRuEbatTleaxe> hey
<kdub> alan_G, WiTH more-cleanup-of-OwnersHiP-Of-CLIenT-buFfers, the chAnGes to BUffer owNErSHIP wiLL probably tricKle into mc::SwITchIngBunDlE, riGHt?
<alan_G> kdub: YeS.
<KduB> i'm finding sOme oF the compoSition CHanges fOR overlaY are tiEd tO thAt clASs
<KdUb> tRyINg tO AnTicIPatE how we'll ChAnGe
<alaN_g> kdUB: i DOn't hAve AnytHing iN flight right nOw - sO you CAn sNeak iN aheaD of mE
<kDub> i dOn't reaLly waNt To wade into it if i Can hElp it, but iT miGhT be NeCessaRY
 * kdub kEepS loOking
<alAn_g> kdub: i Don'T aNTICiPate changing the logIc - JUSt The way buFfers aRE hAnDEd out for ClIenTs. (StILL playIng wITh Raw pointEr vs unIQuE hAndle). So i dOn't antIcIpaTe aNy conFLictS with oVerlays
<kDub> alAN_g, okay. at the momENt, i'm consideriNG bURYiNG the 'FraMeno' logic baCk inSIde oF mc::SWItChiNGBundLe
<alaN_g> KDuB: Is that feasible? SurelY tHere neEds to Be some logic asSociated wiTH THe (possibLy coNCuRRent) compositorS?
 * alan_G decides it IS too late In the Day to worRy
<kdub> the LOGic is neeDed, It jUst SeeMS To Me that the buffER TracKeR is the bEst Place to KeeP it
<KduB> inStEad of spliTting resPoNsIbIlIty Out to THe composItOr aNd The BuffeR TrackeR
<kdub> I'll sEe If ITs cLeaner oR NoT :)
<sAviq> HeY fOlks, SinCe The reCent MIr rElease, uNity8 is craShiNG on sHuTdOwn
<SaviQ> could you pleaSe Have a look hTtPs://bUgs.lauNCHpad.net/mIr/+bug/125
 If you also prefer base_p tr() inste ad of  ma p()  i t'san e asy change...< kdub > alf_, yeah, was just  revi ew i ng
< a lf _> kd ub: (Iw il l pro ba bl y n ee d  t o res ync  with t runk anywa y)<a lf_> kdub: s / tr unk/develo pme nt-branch/
* k dub al wa ysc allsdev elopm ent-br a nch tr unk too
< tr u ebattl e axe> is a ny onehaving any issues wi t h the displaysettin gs af t e r i nst alling mir ?<raca r r> morn i ng < t rue b attleaxe> hey 
<kdub> ala n _g,  withmo re- c leanup -of-o wn e rsh ip-of-clien t-bu ffers, th e chan g es to b u ffer ow nershi p w ill  pro b ab ly  tr ic k lei nt o m c ::S witching Bu nd le, r ight ? < a lan_ g>kdub : yes .
<kdub> i'mfin ding som e ofthe c ompo si tionchange s for  o verlay are tied  tothat clas s
< kd ub>  t rying to ant ici pat e how w e'll ch a nge 
< a l a n_ g> kdub: I don't h av e an ything i n flig h tri g ht now -  s o y ou c a n  snea k in ah ead of m e
<kdu b >idon't r ea lly wa nt  to  wa de in t o it  if ican help  it,b ut it might be necessary
 *k du b ke e ps l ook ing
<alan_g > kd u b: I  don ' tant i cipat e cha ng i ng the logic - just th eway bu ffers  are handed o ut for cli e n t s. (Stil l pl a yi n g with raw poi ntervs uniqueh andle).So Idon't an ticipatea n y confli cts  wi thove r l ay s
<kdub> alan _ g , ok ay . at th e m oment,i'm  co nsi der in g burying  the 'fr am en o'  l ogi c bac k  insideof  mc :: Swi tchin g Bundle 
<ala n_g>  k du b : i s thatf ea s i ble?  S ur elythe re  need s to besome lo gic assoc iat e d wi th  t he (pos sibly concurr en t) composi to rs? 
 * al a n _g decid es it is too late in th e  day to  wo rry
< kdub > the log icis nee ded ,  it ju st see ms to  m e t h a t the b uf fer  t racker ist h e b est p la ce t o keepit
<kdub> insteado f s plitting resp ons ibil i t yout to the  c o mpo s i tor and the buf fer tracke r< kd ub> i'll s e e i fits cle aner or  not: )
<Savi q> hey fo lks, sinc ether e cen t mir rele ase, uni ty8 is cr a shing on  shut dow n
<Sav iq > c ouldyou pl e ase  have  a loo khttps: //bug s. launchpa d.net/mir/+bug/125
 If_you also_prefer base_ptr() instead of_map() it's_an_easy change...
<kdub>_alf_,_yeah, was just_reviewing
<alf_> kdub: (I_will probably need to_resync with trunk_anyway)
<alf_>_kdub: s/trunk/development-branch/
 * kdub always calls development-branch trunk too
<truebattleaxe> is anyone having any issues_with_the display_settings_after_installing mir?
<racarr> morning
<truebattleaxe> hey
<kdub> alan_g,_with more-cleanup-of-ownership-of-client-buffers, the changes to_buffer ownership_will probably trickle into mc::SwitchingBundle, right?
<alan_g> kdub: yes.
<kdub>_i'm_finding some of_the composition changes for overlay are tied to that_class
<kdub> trying to anticipate how we'll_change
<alan_g> kdub: I_don't_have_anything in flight right_now - so you can sneak_in ahead of me
<kdub> i don't_really want to wade into it if_i can help it, but it_might be necessary
 * kdub_keeps looking
<alan_g>_kdub: I don't anticipate changing_the logic -_just the_way buffers are_handed out for clients. (Still playing_with raw pointer_vs unique handle). So I don't_anticipate_any conflicts with_overlays
<kdub>_alan_g,_okay. at_the moment, i'm_considering_burying the_'frameno'_logic back inside of mc::SwitchingBundle
<alan_g> kdub:_is_that feasible? Surely there needs to be_some logic associated with_the_(possibly concurrent) compositors?
 *_alan_g decides it is too_late in the day to worry
<kdub>_the logic_is needed,_it just seems to me that the buffer tracker is the_best place to keep it
<kdub> instead_of splitting responsibility out_to the_compositor_and the buffer_tracker
<kdub>_i'll see_if its cleaner or not :)
<Saviq> hey_folks, since_the recent mir release, unity8 is_crashing on shutdown
<Saviq> could_you_please have a look https://bugs.launchpad.net/mir/+bug/125