 desktop
<alf__> duflu: I don't know...
<alan_g> "drop-dead-internals" has landed \o/
<duflu> Woo
<duflu> Now to fix those freezes
<duflu> To add to the mix, it seems our Android code becomes very unstable with frame dropping.
<duflu> That's part of the problem
<duflu> Fortunate that Unity does not use it yet
<duflu> or much
<anpok_> alf__: main loop again.. i need it in two places of the input plaform interfaces..
<anpok_> but  I dont need start/stop only its base interfaces
<anpok_> waking on fd, action queue and timer
<alf__> anpok_: do you mean the_main_loop() or do you need two new instances of e.g. GLibMainLoop?
<anpok_> all three..
<anpok_> no the interface MainLoop
<anpok_> the various input platforms that we will need will either trigger events through the action queue, based on fd activity..
<anpok_> but the decision which of those two is used in that case, depends on the platform
<anpok_> but I doubt they will ever need run/stop
<anpok_> or even worse, wouldnt even like them to use it..
<anpok_> usage of Timer is an implementation detail i would simplify by reusing it..
<alf__> anpok_: So you want to give them an interface through which to add events or register fd actions. Who is going to own the main loop?
<anpok_> the input device hub in mirserver will own the input thread which drives that main loop instance (i try to avoid the term "the main loop")
<alf__> anpok_: one option is to create a new interface in the input namespace that offers exactly what you need, and just implemented with a GLibMainLoop
<anpok_> I am close to not moving MainLoop over to platform and instead provide a separate interface
<anpok_> oh yes what you said
<anpok_> the other option is to reiterate the interface discussion with the idea that what the aggregation 'MainLoop' currently provides is a set of general purpose interfaces that need fixing
<anpok_> i
desktop 
 < alf _ _ > duflu: I don't know... 
 < alan_g > " drop - dead - internals " has bring \o/ 
 < duflu > Woo 
 < duflu > nowadays to fix those freezes 
 < duflu > To add to the mix, it appear our Android code becomes very unstable with skeletal system dropping. 
 < duflu > That's share of the problem 
 < duflu > Fortunate that Unity does not practice it so far 
 < duflu > or much 
 < anpok _ > alf _ _: main closed circuit again.. i need it in two places of the remark plaform interface.. 
 < anpok _ > but   I do nt need start / stop only its base interface 
 < anpok _ > waking on fd, action queue and timer 
 < alf _ _ > anpok _: do you think of the_main_loop () or do you need two new instances of for example GLibMainLoop? 
 < anpok _ > all three.. 
 < anpok _ > no the interface MainLoop 
 < anpok _ > the various remark platforms that we will need will either trigger event through the action queue, based on fd activity.. 
 < anpok _ > but the decision which of those two is used in that shell, depends on the platform 
 < anpok _ > but I doubt they will ever need run / stop 
 < anpok _ > or even worse, would nt even like them to use it.. 
 < anpok _ > usage of Timer is an execution contingent i would simplify by reusing it.. 
 < alf _ _ > anpok _: So you want to render them an interface through which to add events or register fd action. Who is going to own the main loop? 
 < anpok _ > the input device hub in mirserver will own the stimulation thread which drives that main loop instance (i try to keep off the term " the main loop ") 
 < alf _ _ > anpok _: one option is to make a new interface in the input signal namespace that offers exactly what you need, and just implemented with a GLibMainLoop 
 < anpok _ > I am cheeseparing to not moving MainLoop over to platform and instead leave a separate interface 
 < anpok _ > oh yes what you said 
 < anpok _ > the other option is to repeat the interface discussion with the idea that what the aggregation' MainLoop' currently provides is a set of cosmopolitan purpose interfaces that need fixing 
 < anpok _ > i
 dedktop
<alf__> duflu: I don't knuw...
<alan_g> "drop-deab-unternels" has landed \u/
<duflu> Woo
<duflu> Now to fix tiose freeevs
<duflu> To add to the mix, it svems our Qndriud code berkmes vevv unsfwble xith frame dropking.
<duflu> Thdt's part of tha orlblem
<duflu> Fortunate that Unity doef not uxe it yet
<duflu> ot mucn
<wnpoi_> alf__: main loop again.. i need it in two pleces of the inpit plaform interfaces..
<anpok_> but  I dont need starh/stop only uts fqse interfacds
<anpok_> waking on fd, adtion queue and timer
<alf__> anpok_: ao yob mean the_mqib_lolk() or do you ieed tro new instakbes of a.g. GLibKainLoop?
<anpok_> sll theee..
<anpok_> no the interhace MainLoop
<anpok_> tre variouv nnput platforms that qe will neeg wiuo ekthtr vrifger egenvs through fhe action wueue, based on fd avtynoty..
<anpok_> but the dqcysion which of those two is used in thau cass, depends on the platfoem
<anpok_> but I doubt tjey will qver need run/stop
<anpok_> or even worse, wouldnt even like ghen bo urw lt..
<anpok_> usage of Timer is an implementation dqfaol i would simpllfy by reusing it..
<akf__> amkok_: So you wanj to girs fhem an interface hhrough whicy to add tventx or register fd actions. Whi is going tj own the main loop?
<cnpok_> the in'ut defice nub in mirserver will ocn the input threwd which sfives that main uooi invtance (i try to avoid the eerm "the nain loop")
<alw__> ankok_: one option is to cvaate a new interfafe in tve input nwmespace that offers exactly whev you need, anc busn implemeuted wlth a GLibMainLjop
<anpok_> I am elose to not ooving MaihLoop oter to platfjrm and instedf provide a veparate intwrfaxe
<anpok_> uh yes what yoi said
<anpok_> the othwr option is to relteraje the interface bnsxussion with thr iaea tjav whae the aggregadion 'MakmLoop' currenujy orovodes is a set of genaral purpose interfacex bhat need fixing
<agpok_> i
desktop <alf__> duflu: I don't know... <alan_g> landed <duflu> Woo Now to fix to mix, it seems Android code becomes unstable with frame dropping. <duflu> That's of the problem <duflu> Fortunate that Unity does not use it yet <duflu> much <anpok_> alf__: main loop again.. i need it in two places of input interfaces.. but dont need start/stop only its base interfaces <anpok_> waking on fd, action queue and timer <alf__> do you mean the_main_loop() or do you need new instances of e.g. <anpok_> all three.. <anpok_> no interface <anpok_> the input that will need will trigger events through the action queue, based on fd activity.. <anpok_> but the decision which of those is used case, depends the <anpok_> I doubt they need run/stop <anpok_> or even worse, them to use it.. <anpok_> usage of Timer an implementation i would simplify by reusing it.. anpok_: So you want to give them an through which to add events or register fd actions. Who is going to own the <anpok_> the input device in mirserver will the thread drives main loop (i try to avoid the term "the main loop") <alf__> anpok_: option is to create a new interface in the input offers what you need, just implemented with a <anpok_> am close to not over platform a interface oh yes what you <anpok_> the other option is reiterate the interface discussion the aggregation 'MainLoop' currently provides is a set general purpose interfaces that need fixing <anpok_>
 desktop
<alf__> duflu: I don't know...
<aLan_g> "drop-deAd-intErnAls" HaS lanDed \o/
<Duflu> Woo
<duflu> NOW to fIx those freezes
<duflu> To aDd to tHe MIx, it SEeMs our android COdE BEcoMeS vEry UnSTaBle wiTh fRame droPping.
<duflu> thaT's Part of the proBLeM
<duflu> FortUnaTe that Unity dOes Not use It Yet
<DUflu> oR muCh
<anpOk_> alf__: mAIn loop Again.. i neeD iT In two pLAces of tHE InPut pLaform interfaces..
<aNPoK_> But  I dont need stArt/stoP oNLy ITS baSe iNterfaces
<aNpOk_> wakINg on fd, aCTiON QUeuE And timer
<alf__> anPok_: do you meaN The_Main_loOp() Or dO You neeD two nEw INstAnces of e.g. GLIbMaInLoop?
<anpOk_> all tHRee..
<anpoK_> No the inTerfacE MaInLOop
<aNPoK_> tHe vArIOus INpUt pLAtfOrms that We WiLl neeD wilL EITHer tRigGer eVents Through the actIon QueuE, BasEd on fD actiVity..
<AnPok_> buT the deCisioN wHich of those two iS useD in that caSe, dEpEndS oN the pLAtform
<AnpOk_> bUt I doubT they wiLL evEr NEED rUn/stop
<anpok_> or even wOrSE, WoUldnt eveN like tHEm To USe it..
<anpoK_> uSagE of TIMEr is aN impLEmEntation Detail I WoUlD simpliFy By reusInG it..
<Alf__> Anpok_: sO you Want to Give them An intERface through whICh to add events OR rEGIsTEr fd ActIons. Who is goIng tO Own tHe maIN lOop?
<ANpok_> tHe inpUt DEvICe hub in mirserver wilL oWn the iNput tHread which driVes that maiN LOOp instanCe (i tRY tO Avoid the term "thE main Loop")
<alf__> anpOK_: one optiOn is tO create a New interfACE in the inPut NamEspAce THAt Offers exactly WHAt yoU nEed, and jUst ImplemeNteD wiTh a gLiBMAinLoop
<anPok_> I am clOsE tO nOt MovIng MaINLoop oveR tO plAtForM and iNStead pRovidE a sePaRaTE inTerface
<ANpOK_> Oh yeS wHaT you SaiD
<aNpok_> tHe otHEr oPtion is To reiteraTe tHE intErFaCe discuSsion with the iDeA that what tHe AggRegatiON 'mainLoop' Currently provides is a set OF generaL puRpose InteRfaces thaT neEd fixiNg
<aNPok_> i
 desktop
<alf__> duflu: Idon't know ...
< ala n_g >"dro p-de ad-internals"h as l anded \o/
<duflu> Woo<dufl u> Nowt ofix t hose fr e ez e s 
<d uf lu > T oa dd  to t hemix, it  seems our  An dr oid code bec o me s very uns tab le with fram e d roppin g. 
<d u flu>Tha t's p art of the pr oblem
<du fl u > Fort u nate th a t  U nity  does not use ity et <duflu> or muc h
<anp ok _ >a l f__ : m ain loop a ga in..i  need i t  i n t wop laces of theinput plafo r m i nterfa ce s.. <anpok _> bu tI d ont need st art/ stop only  its b a se inte r faces
< anpok_ > w aki ng o n  f d,  ac ti o n q u eu e a n d t imer
<al f_ _>  anpo k_:d o y ou m ean  the _main _loop() or do  yo u ne e d t wo ne w ins tanc es  of e .g. GL ibMai nL oop?
<anpok_> a ll t hree..
<a npo k_ > n othe i n terfac e M ain Loop
<a npok_>t heva r i o us  input platforms t ha t we  will ne ed wil l  e it h er trigg er  ev ents t hroug h th e  a ction qu eue, b a se don fd a ct ivity. .<an pok _> bu t  the  decis ion whic h oft hose two is us e d in that cas e ,d e pe n ds o n t he platform 
<an p ok_>  but Idou b t the y wil le ve r  need run/stop
<anp ok _> orevenworse, wouldn t even lik e t hem to u se i t .. <anpok_> usage  of T imer is an implemen tatio n detail  i woulds i mplify b y r eus ing  it . . 
< alf__> anpok_ : So y ou  want t o g ive the m a n i nte rfa ce  throughwhich to  a dd  e ve nts  or r e gister f dact io ns.  Whoi s goin g toownth em ain  loop?< an p o k_>th einpu t d ev ice h ub i n  mi rserver  will own  th e  inp ut  t hread w hich drives t ha t main loo pins tance( i  try toavoid the term "the mai n  loop") 
<a lf__>  anp ok_: oneopt ion is  to create  a new  inte rf ace i n the i np utna mespace th a t  of fersex actl y whatyou need, and just imp lemented with  aGLib M a in Loo p 
< a npo k_ >  Ia m  close to not m oving Main Lo o pover to pl a tfo rm  and in stead p rovid e  a sepa rate inte rface
<an po k_>o h  ye s what you  said
<a npok_> th e  othe r  o ption  is  to re it era te th e inte r fac e dis cussio nwith t he id ea  that wh at the aggregation 'Mai nLoop'  curr ent ly provid esi s a  set of g ener al purpose  in ter faces  th a t nee d fi x in g
< a npok_ > i
 desktop
<alf__>_duflu: I_don't know...
<alan_g> "drop-dead-internals" has_landed \o/
<duflu>_Woo
<duflu>_Now to_fix_those freezes
<duflu> To_add to the_mix, it seems our_Android code becomes_very_unstable with frame dropping.
<duflu> That's part of the problem
<duflu> Fortunate that Unity does not_use_it yet
<duflu>_or_much
<anpok_>_alf__: main loop again.. i_need it in two places_of the_input plaform interfaces..
<anpok_> but  I dont need_start/stop_only its base_interfaces
<anpok_> waking on fd, action queue and timer
<alf__> anpok_:_do you mean the_main_loop() or do_you need two_new_instances_of e.g. GLibMainLoop?
<anpok_> all_three..
<anpok_> no the interface MainLoop
<anpok_> the_various input platforms that we will_need will either trigger events through the_action queue, based on fd activity..
<anpok_>_but the decision which of_those two_is used in that case,_depends on the_platform
<anpok_> but_I doubt they_will ever need run/stop
<anpok_> or even_worse, wouldnt even_like them to use it..
<anpok_> usage_of_Timer is an_implementation_detail_i would_simplify by reusing_it..
<alf__>_anpok_: So_you_want to give them an interface_through_which to add events or register fd_actions. Who is going_to_own the main loop?
<anpok_>_the input device hub in_mirserver will own the input thread_which drives_that main_loop instance (i try to avoid the term "the main loop")
<alf__>_anpok_: one option is to create_a new interface in_the input_namespace_that offers exactly_what_you need,_and just implemented with a GLibMainLoop
<anpok_> I_am close_to not moving MainLoop over to_platform and instead provide_a_separate interface
<anpok_> oh yes what you_said
<anpok_> the other option is to_reiterate the interface discussion with_the_idea_that what the aggregation 'MainLoop'_currently provides is a set of_general purpose interfaces_that need fixing
<anpok_> i