 attribute mismatches I say will fail creation are buffer_usage and pixel_format.
<duflu> RAOF: Do we need pixel format for hardware or let GL choose?
<RAOF> Given that we can't let GL choose, yes.
<RAOF> There is literally no way of letting GL choose for us.
<RAOF> (And where people have been proposing such ways, they've been along the lines of âtell GL to use the format that we've already specified for the native windowâ)
<duflu> RAOF: Yes, I mean you can partially infer one from the other, but I guess that only gets you a subset and not a specific singular choice
<RAOF> Right.
<RAOF> And also - your surface creation completes before you do any GL calls.
<duflu> RAOF: Hmm, actually if your buffer creation is deferred then pixel format and buffer usage are also not immediately required -- just needed before the surface ever gets realized
<duflu> Oh, but you have GL wanting things
<duflu> Great
<alf> greyback: Hi! We were discussing implementing the item 'Add a polite "client close your window" request', which I think was requested by you. Could you elaborate what the use case / requirements are for it?
<greyback> alf: it's a desktop feature primarily - to implement the red X in the window decoration
<greyback> which I presume (never checked) is a message to the client to say, please close that window
<greyback> I doubt X just deletes that window on the client
<alf> greyback: ok, so this is per surface (window) not the whole app
<greyback> alf: right
<alf> greyback: (unless they coincide of course)
<greyback> alf: well that's not for Mir to enforce IMO
<greyback> if client has only 1 surface, and user closes it, it's up to the app to decide to close itself or not, no?
<greyback> "close itself" = quit the whole process
<alf> greyback: I wonder... there may be a security risk here I think... imagine a user closing an app, the (only) window disappears, but the process is still there doing its thing in the background
<greyback> alf: isn't it al
attribute mismatches I say will fail creation are buffer_usage and pixel_format. 
 < duflu > RAOF: Do we necessitate pixel format for hardware or lease GL choose? 
 < RAOF > Given that we can't let GL choose, yes. 
 < RAOF > There is literally no means of letting GL choose for us. 
 < RAOF > (And where people have been nominate such way, they've been along the lines of âtell GL to practice the format that we've already specify for the native windowâ) 
 < duflu > RAOF: Yes, I mean you can partially guess one from the other, but I guess that entirely get you a subset and not a specific singular choice 
 < RAOF > Right. 
 < RAOF > And also - your open creation completes before you do any GL call. 
 < duflu > RAOF: Hmm, actually if your buffer creation is deferred then pixel format and buffer use are also not immediately required -- just needed before the surface always gets realized 
 < duflu > Oh, but you have GL wanting things 
 < duflu > Great 
 < alf > greyback: Hi! We were discussing follow through the item' Add a polite " client close your window " request', which I think was requested by you. Could you elaborate what the use event / requirements are for it? 
 < greyback > alf: it's a desktop feature of speech chiefly - to implement the red X in the window decoration 
 < greyback > which I presume (never checked) is a message to the customer to say, please close that window 
 < greyback > I doubt X barely deletes that window on the client 
 < alf > greyback: ok, so this is per surface (window) not the hale app 
 < greyback > alf: right 
 < alf > greyback: (unless they coincide of path) 
 < greyback > alf: well that's not for Mir to enforce IMO 
 < greyback > if client induce only 1 surface, and user closes it, it's up to the app to decide to close itself or not, nobelium? 
 < greyback > " close itself " = quit the whole process 
 < alf > greyback: I wonder... there may be a security risk here I think... imagine a drug user closing an app, the (alone) window disappears, but the procedure is still there act its thing in the setting 
 < greyback > alf: isn't it al
 athribute mismatches I say will fail creajiin are buffed_usage avd pixel_format.
<duflu> RAOF: Do xe nwed puxel format for hardwafe or let GL choowe?
<RAID> Given thef we cak'c let NL chmise, yes.
<RAOF> Thgre is literdlly no way of ldtcing GL choose for us.
<RAOF> (And where [eople nage been proposyng xtch says, they've been along the lines or âtell JL to use the fprmat that we've already spfcifled for the native windowâ)
<duflo> RAJD: Yes, I mean you can partially infgr one from the other, but I guesr thac only gets yiu w subset and not w specific slmgular choice
<TAOF> Right.
<RAOF> Anv alwo - your surface creavion completes beforg you do aty GL calls.
<duflu> RAIF: Hmm, dctudlly uf houd uufrer crfatmon is defedred then puxel format and bufgew usage are alao not iimediately required -- just needed before ths surface ever gets reaoized
<duflu> Oh, but you have GL ranting things
<duflu> Great
<alf> greyback: Hi! We were giscuariny impldnejting the item 'Add a polite "client close your simdpw" request', whigh I think was reqiedtrq by you. Coula you zmagorate what the usf case / requurements wre gor it?
<greyback> alf: it's a dewktop featurv prumarily - to implemznt the red R in tne wimdow decoration
<greyback> whidh I presumf (never cgdcked) is a messaee no tve clienu to say, please cljse that xindoc
<greybacy> I coubt V just delftes bvat window on the flienj
<alf> gseyback: ok, so this is per surface (window) ipt the whole a[p
<ggeyback> ajf: rinht
<alf> greyback: (unless they cpincide of cuurse)
<greybzck> alf: well that's not for Mir dl enforce IMM
<greybach> if cliwnt has unly 1 surface, snd user bljses it, it's up to the epp jo decide to closz utself or not, np?
<grdybwcn> "rlose htself" = quit the whuke prucess
<alf> grcybxck: O wonder... there may ba a aecurity risk here I think... inagine a user closing an app, the (only) wlndow dirappesrs, but the process is still thers doing ihs bhing in the facknrougd
<greyback> alf: isn't it al
attribute mismatches I say will fail creation and <duflu> RAOF: we need pixel GL <RAOF> Given that can't let GL yes. <RAOF> There is literally no of letting GL choose for us. <RAOF> (And where people have been proposing ways, they've been along the lines of âtell GL to use the format we've specified the windowâ) <duflu> RAOF: Yes, I mean you can partially infer one from the other, but I that only gets you a subset and not specific singular choice <RAOF> <RAOF> And also - your creation before you any calls. RAOF: Hmm, actually your buffer creation is deferred then pixel format and buffer usage are also not immediately required -- needed before ever gets <duflu> but have GL wanting Great <alf> greyback: Hi! We were item 'Add a polite "client close your window" which I was requested by you. Could you what the use case / requirements are for <greyback> alf: it's a desktop feature primarily - to implement the red X in the <greyback> which I presume checked) is a to client say, close that <greyback> I doubt X just deletes that window on the client greyback: ok, so this is per surface (window) not the <greyback> right <alf> greyback: they coincide of course) alf: that's not for Mir IMO if 1 and closes it, it's up the app to decide to itself or not, no? the whole process <alf> greyback: I wonder... there be a security risk here I think... a user closing an app, the (only) window disappears, but the process still there thing in the background <greyback> alf: isn't it
 attribute mismatches I say wiLl fail creaTion aRe bUffEr_UsagE and Pixel_format.
<dufLU> RAOf: Do we need pixel format foR hardWaRE or lET Gl chooSe?
<RAOF> GIVeN THat We CaN't lEt gl cHoose, Yes.
<rAOF> TheRe is literaLly No Way of letting gl cHoose for us.
<rAOf> (And where peoPle Have beEn ProPOsing SucH ways, They've BEen aloNg the lineS oF Âtell Gl To use thE FOrMat tHat we've already speCIfIEd for the native WindowÂ)
<dUFlU> raOF: yes, i mean you caN pArtiaLLy infer ONe FROM thE Other, but I guesS that only geTS yoU a subsEt And NOt a speCific SiNGulAr choice
<RAOf> RigHt.
<RAOF> And Also - yoUR surfacE CreatioN complEteS beFore YOu Do Any gL CAllS.
<DuFlu> raOF: hmm, actuaLlY iF your BuffER CREatiOn iS defErred Then pixel formAt aNd buFFer Usage Are alSo noT iMmediAtely rEquirEd -- Just needed beforE the Surface evEr gEtS reAlIzed
<dUFlu> Oh, bUt yOu hAve GL waNting thINgs
<DuFLU> grEat
<alf> greyback: Hi! We WeRE DiScussing ImplemENtInG The item 'ADd A poLite "CLIent cLose YOuR window" rEquest', WHiCh i think wAs RequesTeD by You. could YOu elAboratE what the Use caSE / requirements aRE for it?
<greybacK> AlF: IT's A DeskTop Feature primArilY - To imPlemENt The REd X in The wiNdOW dECoration
<greyback> whiCh i presuMe (nevEr checked) is a mEssage to thE CLIent to saY, pleASe CLose that window
<GreybAck> I doubt X JUst deletEs thaT window oN the clienT
<ALf> greybaCk: oK, so ThiS is PER sUrface (window) nOT The wHoLe app
<grEybAck> alf: rIghT
<alF> grEybAcK: (unless thEy coinciDe Of CoUrSe)
<gReybaCK> alf: well ThAt's NoT foR Mir tO EnforcE IMO
<gReybAcK> iF CliEnt has oNLy 1 SURfacE, aNd User CloSeS it, it'S up tO The App to deCide to cloSe iTSelf Or NoT, no?
<greyBack> "close itseLf" = Quit the whoLe ProCess
<alF> GReyback: I Wonder... there may be a securiTY risk heRe I Think... ImagIne a user cLosIng an aPp, tHE (only) wIndow dIsappEaRs, bUT The prOCEsS is StIll there doING itS thinG iN the BackgroUnd
<greyback> alf: isn't IT al
 attribute mismatches I sa y will fai l cre ati onar e bu ffer _usage and pix e l_fo rmat.
<duflu> RAOF: Do  we n ee d  pix e lforma t for h a rd w a reor  l etGL ch oose? 
<R AOF> Gi ven that w e c an 't let GL ch o os e, yes.
<R AOF > There is l ite rallyno  wa y  of l ett ing G L choo s e forus.
<RAOF >( And wh e re peop l e  h avebeen proposing su c hw ays, they've b een al on g  t h e  li nes  of âtel lGL to use the fo r m a t t h at we've alre ady specifi e d f or the  n ati v e wind owâ )< duf lu> RAOF: Y es,I mean yo u canp artiall y  inferone fr omthe  oth e r,  b utIg ues s  t hat onl y gets y ou  a  subs et a n d n ot a  sp ecif ic si ngular choice 
<R AOF> Rig ht.
< RAOF>  And  a lso -  yoursurfa ce  creation compl etes  before y oudo  an yGL ca l ls.
<d ufl u>RAOF: H mm, act u all yi f yo ur buffer creation  i s de ferred t hen pi x el  f o rmat and  b uff er u s a ge ar e al s onot imme diatel y  r eq uired - -just n ee ded  be foret he s urface  ever ge ts re a lized
<duflu>O h, but you ha v eG L  w a ntin g t hings
<dufl u> G r eat<alf >  g rey b ack:Hi! W ew er e  discussing impleme nt ing th e ite m 'Add a poli te "client c l ose your  win d ow "  request', whi ch Ithink wasr equested  by y ou. Coul d you ela b o rate wha t t heuse  ca s e  /  requirements a re f or  it?
<g rey back> a lf:  it 'sa d es ktop feat ure prim ar il y-toimple m ent there d X  i n t he wi n dow de corat ion<g re y bac k> whic h  I p resu me  ( neve r c he cked)  isa  me ssage t o the cli ent to s ay ,pleaseclose that wi nd ow
<greyba ck > I  doubt X  just de letes that window on th e  client 
<a lf> g reyb ack: ok,sothis i s p e r surf ace (w indow )not t he wh o l eapp 
< greyback>a l f:right 
< alf>  greyba ck: (unless they c o inc ide of course )
< grey b a ck > a l f: wel lt hat ' s  not for Mir to  enforce I MO <g reyback> i f  cl ie nt hasonly 1surfa c e, anduser clos es it, it 's  upt o  th e app to d ecide to  close it s elf o r  n ot, n o?<greyb ac k>"clos e itse l f"= qui t thewh ole pr ocess 
< alf> gre yback: I wonder... ther e maybe asec urity ris k h e reI think.. . im agine a us erclo singana pp, t he ( o nl y)w indow  dis a ppears, b u tthe p ro cess is sti l l the re do ing its th ingin the background <greyback> alf : is n ' t i t a l 
 attribute_mismatches I_say will fail creation_are buffer_usage_and_pixel_format.
<duflu> RAOF:_Do_we need pixel_format for hardware_or let GL choose?
<RAOF>_Given that we_can't_let GL choose, yes.
<RAOF> There is literally no way of letting GL choose for_us.
<RAOF>_(And where_people_have_been proposing such ways, they've_been along the lines of_âtell GL_to use the format that we've already specified_for_the native windowâ)
<duflu>_RAOF: Yes, I mean you can partially infer one_from the other, but I guess_that only gets_you_a_subset and not a_specific singular choice
<RAOF> Right.
<RAOF> And also_- your surface creation completes before_you do any GL calls.
<duflu> RAOF: Hmm,_actually if your buffer creation is_deferred then pixel format and_buffer usage_are also not immediately required_-- just needed_before the_surface ever gets_realized
<duflu> Oh, but you have GL_wanting things
<duflu> Great
<alf>_greyback: Hi! We were discussing implementing_the_item 'Add a_polite_"client_close your_window" request', which_I_think was_requested_by you. Could you elaborate what_the_use case / requirements are for it?
<greyback>_alf: it's a desktop_feature_primarily - to implement_the red X in the_window decoration
<greyback> which I presume (never_checked) is_a message_to the client to say, please close that window
<greyback> I doubt_X just deletes that window on_the client
<alf> greyback: ok,_so this_is_per surface (window)_not_the whole_app
<greyback> alf: right
<alf> greyback: (unless they coincide_of course)
<greyback>_alf: well that's not for Mir_to enforce IMO
<greyback> if_client_has only 1 surface, and user_closes it, it's up to the_app to decide to close_itself_or_not, no?
<greyback> "close itself" =_quit the whole process
<alf> greyback: I_wonder... there may_be a security risk here I think..._imagine_a user closing an app, the_(only)_window disappears, but the process is_still_there_doing its thing in the_background
<greyback> alf: isn't it al