On 24/4/12 5:25, Jürgen Hestermann wrote:
I wanted to write a program that has no window but may show messages to
the user.
I have lots of such programs written with Virtual Pascal but I am
struggling
to do the same with Free Pascal/Lazarus.
A simple test program would look like this:
-
I wanted to write a program that has no window but may show messages to
the user.
I have lots of such programs written with Virtual Pascal but I am
struggling
to do the same with Free Pascal/Lazarus.
A simple test program would look like this:
program Test;
{$m
If I hit Alt+Up on "RemoveDir" within my program I am moved to
D:\Programme\lazarus\fpc\2.6.1\source\rtl\objpas\sysutils\diskh.inc(21,10)
with the function header declaration but when doing it again
on "RemoveDir" within this file I get:
Error: identifier not found: RemoveDir
so I can't see the
Marco van de Voort wrote:
In our previous episode, Mark Morgan Lloyd said:
Marco, I see you had a StackOverflow question on this a year or so ago.
Did you ever get anywhere with it in practice?
It was an idea to lower the overhead and improve the reliability of our
serial protocol. (because of
In our previous episode, Mark Morgan Lloyd said:
> Marco, I see you had a StackOverflow question on this a year or so ago.
> Did you ever get anywhere with it in practice?
It was an idea to lower the overhead and improve the reliability of our
serial protocol. (because of the out of band informat
Marco, I see you had a StackOverflow question on this a year or so ago.
Did you ever get anywhere with it in practice?
I'm about to hack a SerBreak() into my re-implementation of serial.pp,
and since I have dedicated HP comms test gear here I could check that it
was interleaving with dataflow
In our previous episode, Jonas Maebe said:
> > It is hard because 2.6.x uses a different makefile system compared to trunk,
> > which is harder to tune for specific OSes.
>
> Now it is broken for Darwin ("fpc-2.2" = fixes branch in this context):
Fixed I hope.
__
I'm using tLTcp with tLEventer. I've set tLTcp.eventer to the associated
tLEvent object and call tLEvent.callAction to wait for new events. After a
socket disconnected, OnDisconnect gets called shipped with an aSocket:tLSocket
parameter.
Should I call aSocket.destroy explicitly to prevent the d
marcov wrote on Mon, 23 Apr 2012:
In our previous episode, Reinier Olislagers said:
Perhaps some of these revisions in trunk could be backported:
r20692 | marco | 2012-04-02 13:46:51 +0200 (ma, 02 apr 2012) | 2 lines
It is hard because 2.6.x uses a different makefile system compared to trunk
