On 09:31 AM, Paul Breneman wrote: > On 02:32 AM, Bob Axtell wrote: >> This newbie is familiar with COMPORT from WINSOFT from my olden Delphi >> days, but I can no longer afford it for one program. >> >> Does anybody know of a free/cheap component? Any how does it install? > > www.CtrlTerm.com uses Synapse and Synaser and there is a port for Lazarus. I should have mentioned that www.CtrlTerm.com is a simple example of how Synapse and Synaser can be used (it is not the component itself).

Beads start at $25.00. We have a limited selection of personalized mother’s jewelry available in store. We may be able to help! We have beads to celebrate seasons, hobbies and holidays just like Mother’s Day. Mother’s Jewelry Looking for a meaningful gift at the last minute? Descargar gratis antivirus que elimine recycler bong.

Best regards, Paul www.TurboControl.com -- _______________________________________________ Lazarus mailing list. On 10:53 PM, Roberto P. Wrote: > I'd like to point out that CPortLaz is multithreaded Does it work similar to AsyncPro? In fact, IMHO, it would be desirable to have a component that _internally_ uses TThread to handle blocking ports (either using just a byte-FIDO - this is what AsyncPro does - and/or allowing the user to implement a protocol within the Thread's 'Execute' ), and when some information from the port is received (at least one byte or when the protocol handler issues a 'ready'), does an Event (aka queued callback) to the main thread. The main thread call of course needs to be 'scheduled' using means such as TThread.Queue or Application.QueueAsyncCall.

Projects using Lazarus/de. It provides a visual serial port (TSdpoSerial) implementation of Synaser, an IEEE1394 camera. Uses synedit for syntax highlighting, and uses the Lazarus Component Library (LCL) is a set of visual and non-visual component classes over a Widget toolkit-dependent layer with multi-language support (English-Turkish). This page describes various ways of accessing hardware devices on Lazarus. These devices include, but are not limited to: ISA, PCI, USB, parallel port, serial port.

(As at the time when AsyncPro was released, Delphi did not provide either, AsyncPro uses Windows Messages by directly accessing the Windows API, which happily is not necessary with Lazarus). Unfortunately Thread -> Mainthread signaling is only easily provided in Lazarus in the GUI based Widget Types. (NoGUI still needs an appropriate enhancement.) But of course the user (or even a ComPort Unit) could provide a usable Main Loop implementation. -Michael -- _______________________________________________ Lazarus mailing list. On 10:53 PM, Roberto P. Wrote: I'd like to point out that CPortLaz is multithreaded Does it work similar to AsyncPro?

In fact, IMHO, it would be desirable to have a component that _internally_ uses TThread to handle blocking ports (either using just a byte-FIDO - this is what AsyncPro does - and/or allowing the user to implement a protocol within the Thread's 'Execute' ), and when some information from the port is received (at least one byte or when the protocol handler issues a 'ready'), does an Event (aka queued callback) to the main thread. The main thread call of course needs to be 'scheduled' using means such as TThread.Queue or Application.QueueAsyncCall. (As at the time when AsyncPro was released, Delphi did not provide either, AsyncPro uses Windows Messages by directly accessing the Windows API, which happily is not necessary with Lazarus). Unfortunately Thread -> Mainthread signaling is only easily provided in Lazarus in the GUI based Widget Types. (NoGUI still needs an appropriate enhancement.) But of course the user (or even a ComPort Unit) could provide a usable Main Loop implementation.