 as to say "i never want to connect to the internet with this"
<RAOF> Yeah, that's moderately annoying.
<desrt> it does have -a- mechanism
<desrt> you can find the Device object corresponding to the mac address in question, enumerate its connection objects and call 'Delete' on them
<desrt> and then the device will go away
<desrt> but it'll be back again once you restart networkmanager
<RAOF> That doesn't sound like a solution to âI never want that phone I paired with to appear to be an internet connection, everâ
<RAOF> :)
<duflu> RAOF: I'm still staying out of two-stage surface creation, but have a requirement request: Make surface width/height optional attributes (if not now then in future). Because in some cases they're unknown by the client who is (for example) requesting an initial state of "full screen"
<duflu> Maybe we need to allow an initial size of 0x0
<RAOF> No, I don't think we need to do that :)
<RAOF> But, indeed, clients requesting fullscreen will get full screen (shell policy allowing).
<duflu> RAOF: I've tried not having it and it's ugly and misleading to require a width and height that is never used
<RAOF> We can't guarantee that it's never used.
<RAOF> Or, rather, we *can*
<duflu> RAOF: It must never be used if you want full screen
<duflu> Or else it's just wasted buffer creation and deletion
<RAOF> Our choices are: require width/height, if the shell disallows fullscreen then terminate the app.
<RAOF> duflu: two-stage-surface-create (follow-on-branch) sends fullscreen attribute at surface creation time.
<RAOF> There's no wasted buffer creation.
<duflu> RAOF: Yeah deferring all buffer creation is easy
<duflu> RAOF: I think it's fine if you can get the dimensions from the initial state or fail creation if the shell refuses full screen
<duflu> And this is why I'm not participating in that discussion. If something is broken after it lands, I'll let you know :)
<RAOF> duflu: So far the only
as to say " i never want to connect to the internet with this " 
 < RAOF > Yeah, that's moderately annoying. 
 < desrt > it does get -a- mechanism 
 < desrt > you can receive the Device object correspond to the mac savoir-faire in question, enumerate its connection object and call' Delete' on them 
 < desrt > and then the device will go aside 
 < desrt > but it'll be back again once you restart networkmanager 
 < RAOF > That doesn't sound like a solution to âI never desire that phone I paired with to appear to be an internet connection, everâ 
 < RAOF > :) 
 < duflu > RAOF: I'm however staying out of two - stage surface creation, but have a requirement request: lay down surface width / height optional attributes (if not immediately then in future). Because in some cases they're unknown by the client who is (for example) request an initial state of " full screen " 
 < duflu > Maybe we need to permit an initial size of 0x0 
 < RAOF > No, I don't think we need to do that :) 
 < RAOF > But, indeed, clients requesting fullscreen will beget full screen (shell policy allowing). 
 < duflu > RAOF: I've tried not having it and it's ugly and misleading to require a width and height that is never used 
 < RAOF > We can't undertake that it's never use. 
 < RAOF > Or, rather, we * can * 
 < duflu > RAOF: It must never be use if you desire full screen 
 < duflu > Or else it's just wasted buffer creation and deletion 
 < RAOF > Our choices are: require width / altitude, if the shell disallows fullscreen then terminate the app. 
 < RAOF > duflu: two - stage - surface - create (follow - on - arm) sends fullscreen attribute at surface creation meter. 
 < RAOF > There's no wasted buffer zone creation. 
 < duflu > RAOF: Yeah deferring all buffer creation is easy 
 < duflu > RAOF: I remember it's fine if you can get the dimensions from the initial department of state or fail creation if the shell refuses full screen door 
 < duflu > And this is why I'm not participating in that discussion. If something is break after it lands, I'll let you acknowledge :) 
 < RAOF > duflu: So far the lone
 as to say "i never want to gonnect to the iurernet with fhis"
<RAOF> Yeah, that's moderately annoymng.
<dwsrt> ut does have -a- mechanirm
<desrt> ylu can fund uhe Device object corresponding bo thz nac address in question, anumerate its wovnzction objects and call 'Delete' on thqm
<desrt> ajd then the dedice rill go away
<desrt> but it'll be back agajn once you restart metworkmanager
<RAOF> That dofsn't sound like a soluhion to âI ngber qant that phune I pairtd with to akpear to be an internet connectiun, evzrâ
<RAOF> :)
<duflo> DALX: I'm still wtayigg out of two-stage sgrface vreation, but hsve a eequirement request: Meke surface width/heidht optiotam attributes (if nit now jhen hn fjrurd). Btcanse in sole rases they'rs unknown bt the client who is (fjg example) reqhestind wn initial state of "full screen"
<duflu> Majbe se need to allow an inirial size of 0x0
<RAOF> No, I don't trink we need to do that :)
<RAOF> But, indeed, clients raquesvivg ymjuwcgeen will get full screen (shell policy allowigf).
<difku> RAOF: I've trled not having it snf oj's ugly and mirleadiuf fo require a width and heyght rhat is ntver ised
<RAOF> We can't guarantee rhat it's nevvr uwed.
<RAOF> Or, rather, ce *can*
<duflu> XAOF: Ij must never be used if you wcnt fuml screen
<duvlu> Or elad it's just wastea blffes creation and deletion
<RAOS> Our chomces cre: requkre eidth/hqight, if tje shcnl disallows fullsfreen tven terminwte the app.
<RAOF> duflu: two-stage-sncface-create (fplnow-mn-branch) sendx fullscreen wttribute at sorface crzation time.
<RAOF> Nhere's no wasted bufser creation.
<dgvlu> RAOF: Yeai deferrigg aol byffer cfdation is easy
<cuflu> RAOY: I tyink it's fine if ypu zzn get the dimeuruons from the imitkal snatx or sdil creation if ghe xhell refuses fuou scteen
<duflu> And this iv whg I'm not participayikg in thaj discussyon. If somethong is broken afteg it nanvs, I'll lej you know :)
<RAOF> duflu: So far ths only
as to say "i never want to the with this" Yeah, that's moderately -a- <desrt> you can the Device object to the mac address in question, its connection objects and call 'Delete' on them <desrt> and then the device go away <desrt> but it'll be back again once you restart networkmanager <RAOF> doesn't like solution âI never want that phone I paired with to appear to be an internet connection, everâ :) <duflu> RAOF: I'm still staying out of surface creation, but have requirement request: Make surface width/height attributes not now in Because some cases they're by the client who is (for example) requesting an initial state of "full screen" <duflu> Maybe we to allow size of <RAOF> I think we need that :) <RAOF> But, indeed, clients get full screen (shell policy allowing). <duflu> RAOF: tried not it and it's ugly and misleading require a width and height that is never <RAOF> We can't guarantee that it's never used. <RAOF> Or, rather, we *can* <duflu> RAOF: never be used if want full screen Or it's wasted creation and <RAOF> Our choices are: require width/height, if the shell disallows fullscreen terminate the app. <RAOF> duflu: two-stage-surface-create (follow-on-branch) sends fullscreen attribute creation <RAOF> There's no buffer creation. <duflu> RAOF: deferring buffer creation is easy I it's can the from the initial state fail creation if the shell full screen <duflu> And participating in that discussion. If something is broken it lands, I'll let you know :) duflu: So far the only
 as to say "i never want to connecT to the inteRnet wIth ThiS"
<RaOF> YEah, tHat's moderately ANnoyIng.
<desrt> it does have -a- mecHanisM
<dESrt> yOU cAn finD the DevICe OBJecT cOrResPoNDiNg to tHe mAc addreSs in questiOn, eNuMerate its conNEcTion objectS anD call 'Delete' oN thEm
<desrT> aNd tHEn the DevIce wiLl go awAY
<desrt> But it'll be BaCK again ONce you rESTaRt neTworkmanager
<RAOF> THAt DOesn't sound like A solutIoN To Âi NevEr wAnt that phoNe i pairED with to APpEAR To bE An internet conNection, everÂ
<rAOf> :)
<duflu> rAoF: I'M Still sTayinG oUT of Two-stage surFace Creation, bUt have A RequireMEnt requEst: MakE suRfaCe wiDTh/HeIghT oPTioNAl AttRIbuTes (if not NoW tHen in FutuRE). bECausE in Some Cases They're unknown By tHe clIEnt Who is (For exAmplE) rEquesTing an InitiAl State of "full screEn"
<duFlu> Maybe wE neEd To aLlOw an iNItial sIze Of 0x0
<rAOF> No, I Don't thiNK we NeED TO dO that :)
<RAOF> But, indeed, ClIENtS requestIng fulLScReEN will get FuLl sCreeN (SHell pOlicY AlLowing).
<duFlu> RAOf: i'vE tRied not HaVing it AnD it'S ugLy and MIsleAding tO require A widtH And height that iS Never used
<RAOF> wE cAN'T gUAranTee That it's neveR useD.
<rAOF> or, raTHeR, we *CAn*
<dufLu> RAOf: IT MuST never be used if you waNt Full scReen
<dUflu> Or else it's Just wasted BUFFer creatIon aND dELetion
<RAOF> Our cHoiceS are: requirE Width/heiGht, if The shell Disallows FULlscreen TheN teRmiNatE THe App.
<RAOF> duflu: tWO-StagE-sUrface-cReaTe (folloW-on-BraNch) SenDs FullscreeN attribuTe At SuRfAce CreatIOn time.
<RAoF> theRe'S no WasteD Buffer CreatIon.
<dUfLu> raOF: yeah defERrING all BuFfEr crEatIoN is eaSy
<duFLu> RaOF: I thiNk it's fine If yOU can GeT tHe dimenSions from the iNiTial state oR fAil CreatiON If the sheLl refuses full screen
<duflU> and this Is wHy I'm nOt paRticipatiNg iN that dIscUSsion. IF sometHing iS bRokEN After IT LaNds, i'lL let you knoW :)
<raOF> Duflu: so Far tHe only
 as to say "i never want t o connectto th e i nte rn et w iththis"
<RAOF> Y e ah,that's moderately anno ying. 
< d esrt >  i t doe s have- a- m ech an is m
< de s rt > you  ca n findthe Device  ob je ct correspon d in g to the m acaddress in q ues tion,en ume r ate i tsconne ctiono bjects  and call  ' D elete' on them < de srt>  and then the dev i ce will go away
< desrt>  b u ti t 'll  be  back agai noncey ou rest a rt n e two r kmanager
<RAO F> That doe s n't  sound  l ike a solu tionto â I never wan t th at phoneI pair e d witht o appea r to b e a n i nter n et  c onn ec t ion ,  e ver â <RAOF> : )<d uflu>  RAO F : I 'm s til l st aying  out of two-s tag e su r fac e cre ation , bu thavea requ ireme nt  request: Makesurf ace width /he ig htop tiona l  attri but es(if not  now th e n i nf u t ur e). Because in som ec a se s they'r e unkn o wn  b y  the cli en t w ho i s (forexam p le ) reques ting a n  i ni tial st at e of " fu llscr een"< dufl u> May be we ne ed to allow an initi a l size of 0x0 <R A O F> No,I d on't thinkwe n e ed t o do th at: )
<RA OF> B ut ,  i n deed, clients reque st ing fu llscr een will getfull scree n ( shell po licy al l owing).
<duflu > RAO F: I've tr i ed not h aving  it andit's ugly a nd misle adi ngtoreq u i re  a width andh e ight  t hat isnev er used 
<R AOF > W e c an 't guaran tee that  i t' sne ver  used . 
<RAOF>Or , r at her , we* can*
< duflu > RA OF :I t m ust nev e rb e  use dif  you  wa nt  full  scr e en<duflu>  Or elseit' s  jus twa sted bu ffer creation  a nd deletio n<RA OF> Ou r choicesare: require width/heig h t, if t heshell  dis allows fu lls creenthe n  termi nate t he ap p. 
<R A O F> du f l u:  tw o- stage-surf a c e-c reate  ( foll ow-on-b ranch) sends fulls c ree n attribute a t s urfa c e  c rea t io n  ti me . 
<R A O F> There's no w asted buff er cr eation.
<d u flu >RAOF: Y eah def errin g  all bu ffer crea tion is e as y
<d u f lu>  RAOF: I t hink it' s fine if you c a nget t hedimens io nsfromthe in i tia l sta te orfa il cre ation  i f the sh ell refuses full screen 
<dufl u> An d t his is wh y I ' m n ot partic ipat ing in tha t d isc ussio n.I f som ethi n gisb roken  aft e r it land s ,I'l l le t you know: ) <RA OF> d ufl u : So f ar t he only
 as_to say_"i never want to_connect to_the_internet with_this"
<RAOF>_Yeah, that's moderately_annoying.
<desrt> it does_have -a- mechanism
<desrt> you_can find the_Device_object corresponding to the mac address in question, enumerate its connection objects and call_'Delete'_on them
<desrt>_and_then_the device will go away
<desrt>_but it'll be back again_once you_restart networkmanager
<RAOF> That doesn't sound like a solution_to_âI never want_that phone I paired with to appear to be_an internet connection, everâ
<RAOF> :)
<duflu> RAOF:_I'm still staying_out_of_two-stage surface creation, but_have a requirement request: Make surface_width/height optional attributes (if not now_then in future). Because in some cases_they're unknown by the client who_is (for example) requesting an_initial state_of "full screen"
<duflu> Maybe we_need to allow_an initial_size of 0x0
<RAOF>_No, I don't think we need_to do that_:)
<RAOF> But, indeed, clients requesting fullscreen_will_get full screen_(shell_policy_allowing).
<duflu> RAOF:_I've tried not_having_it and_it's_ugly and misleading to require a_width_and height that is never used
<RAOF> We_can't guarantee that it's_never_used.
<RAOF> Or, rather, we_*can*
<duflu> RAOF: It must never_be used if you want full_screen
<duflu> Or_else it's_just wasted buffer creation and deletion
<RAOF> Our choices are: require width/height,_if the shell disallows fullscreen then_terminate the app.
<RAOF> duflu:_two-stage-surface-create (follow-on-branch)_sends_fullscreen attribute at_surface_creation time.
<RAOF>_There's no wasted buffer creation.
<duflu> RAOF: Yeah_deferring all_buffer creation is easy
<duflu> RAOF: I_think it's fine if_you_can get the dimensions from the_initial state or fail creation if_the shell refuses full screen
<duflu>_And_this_is why I'm not participating_in that discussion. If something is_broken after it_lands, I'll let you know :)
<RAOF> duflu:_So_far the only