On 27.06.2017 14:37, Lukasz Sokol wrote:
But I'd put the serial port handling calls, blocking or not, into a
thread separate from main anyway.
Of course. (The "short message says this, too.)
(p.s. why not reply on the group still? :) )
I did send the message to the group, as well, but those
On 27.06.2017 12:10, Lukasz Sokol wrote:
The serial handling thread would poll the serial port ...
As already pointed out above (in a very short message) no need for
polling, just use blocking OS calls.
-Michael
___
fpc-pascal maillist -
On 27.06.2017 00:28, Bo Berglund wrote:
I have the concern that I am using Application.Processmessages, which
I believe cannot be used in a console program.
How can I replace it?
TThread.Queue is available in an appropriately done "console application".
As already discussed several times in
On Tue, Jun 27, 2017 at 11:52 AM, African Wild Dog
wrote:
> There are some parts of your article which are in English and you have added
> a link to another article, so it helped me a lot. Thanks for your reply.
You are welcome.
Regards,
Marcos Douglas
2017-06-26 12:45 GMT-03:00 Marcos Douglas B. Santos :
>
> Hi,
>
> I wrote an article about it https://goo.gl/Lij4hu
> But you need to translate from Portuguese to English.
>
> Best regards,
> Marcos Douglas
>
There are some parts of your article which are in English and you
On 26/06/17 23:28, Bo Berglund wrote:
[...]
>
> NEXT:
> It looks like I will have to rewrite my relaying program now used in
> Windows for the conversion to TCP from RS232 to also work as the
> replacement for ser2net on RPi3. This way I can monitor the data
> better and check time intervals etc.
On 26/06/17 22:30, Bo Berglund wrote:
My problem here is the fact that the RPi is headless so the GUIprogram I have
written with Lazarus will not work. Instead I have tomake a console version
that can run on RPi for the test and here Ihave the concern that I am using