[Gambas-user] Serial Port Change Events Not Working after Upgrade to Karmic

[Tony]

   Benoît Minisini wrote:

I found out that reading one by one is a slow process,
I found out that reading all Lof will in a rare instance _READ will not
 fire when only 1 byte arrives immediately after.
I find it works correctly 100% when I read Lof()-1 and rely on _Read to
 fire again. for the one remaining and the new one arriving immediately
 after.

    

Uh... Very strange! It would be cool if you could try your program with the 
latest Gambas 2 or Gambas 3 and see if you have to do the same trick.

Regards,

  

   Hi all,
   I'd just like to report that with revision 2459, the change events have been
   restored for my application. I tried flowcontrol none/hardware/software/both
   and couldn't pick any appreciable difference in CPU utilisation. The funny
   thing is that the anomoly reported in a previous email -  " The application
   also uses the UDPsocket to communicate remotely and what I have noticed is
   that if the serial port does not open correctly e.g. /dev/tty wrong and the
   UDPsocket is open, then there is a large amount of CPU used. Both open
   correctly and CPU normal" - appears to be fixed. Whilst I don't understand
   why this has been fixed, it would seem to be another plus.
   Regards,
   Tony.