> > Yes, I'll look at that, but why in the Ready event? Would there be any > disadvantage or problem with setting the socket to block permanently > when it is instantiated and its properties setup in code? Also, if it > is set in the Ready event, would it needlessly get set again every > time the socket became ready? >
I would do that there because I'm sure the socket is opened once the socket is connected. Otherwise setting the Blocking property won't work. I can modify the stream class so that you can set the Blocking property even if the stream is not opened, but at the moment it does not work like that! Regards, -- Benoît Minisini ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
