On 18.06.2017 18:16, Bo Berglund wrote:
No RS232 work with FPC/Lazarus
earlier and in Delphi I used AsyncPro components, but these are so
complex that one is lost amongst all properties to set...
AsyncPro is free and easy to use but not perfectly bug-free.
Unfortunately no fpc/Lazarus port ye
On 2017-06-19 01:35, James Richters wrote:
The problem is not with rendering with rgb565, the problem is something in the
original that was patched with the setcolor function:
Line 122 of agg_color pas has:
constructor rgba8.Construct;
begin
b{*}:=int8u(r_ );
g:=int8u(g_ );
r:=int8u(b_ );
On Mon, 19 Jun 2017 09:25:59 -0400, Paul Breneman
wrote:
>I've used com0com *and* hub4com successfully for several things in the
>past. See #3 here:
> http://www.ctrlterm.com/related.htm
>
In the README file with com0com they write:
"INSTALLING
==
NOTE (x64-based Windows Vista/Wind
On 06/19/2017 08:43 AM, Bo Berglund wrote:
On Sun, 18 Jun 2017 19:16:05 -0400, Paul Breneman
wrote:
Why do you need FPC code? Here are free drivers that work in Windows:
http://com0com.sourceforge.net/
...
I would really like to use an available program rather than spening
time to deve
On Sun, 18 Jun 2017 19:16:05 -0400, Paul Breneman
wrote:
>Why do you need FPC code? Here are free drivers that work in Windows:
> http://com0com.sourceforge.net/
I tried again and failed again.
I installed com0com and had an error in my face during installation:
SetupUninstallOEMInf(oem11.inf
On Sun, 18 Jun 2017 19:16:05 -0400, Paul Breneman
wrote:
>Why do you need FPC code? Here are free drivers that work in Windows:
> http://com0com.sourceforge.net/
Because I am programming in Pascal (Delphi and FPC) and I had failed
to find any working ready-made solutions.
It looks like I hav
On 2017-06-16 01:51, James Richters wrote:
Yeah, probably not the best naming convention.
>
Perhaps some comments at the top of both units explaining the
difference and also mentioning the other unit exits would save some
confusion
I have applied such a change. So far only to the Agg2D and a
