There is currently no ICS for C# version. But there is a Delphi.NET version.
Normally that version should be usable directly from C# provided you build
an assembly using Delphi.NET (If you have BDS2006, you can do both
Delphi.NET and C# at the same time).
Note that if you really need a pure C#
Does anyone already used ICS in C# in async mode ?
Can you tell me how I have to do that.
I want to use a TCPclient.
Regards,
Eric Verstrepen
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.2/422 - Release Date: 17/08/2006
--
Angus Robertson - Magenta Systems Ltd wrote:
>> Unfortunately the callback requires a window handle as well.
>
> But zero is fine for the handle. I use this code in a DLL to close
> a database on inactivity.
Thanks Angus, sometimes, especially after a 16 hours day it may
happen that I even forge
Francois PIETTE wrote:
>> Unfortunately the callback requires a window handle as well.
>
> And what is the problem ? Use the TWSocket handle.
Thanks, I must have had a blackout yesterday evening.
The handle of the window used by Windows internally is
passed.
---
Arno Garrels [TeamICS]
http://www
Hello Brian,
> I'm eager now to try ICS.
Good :)
> Out of curiosity, is the behavior of the D5 TServerSocket (in non-blocking
> mode) the same as ICS? I've used the D5 component in the past and have run
> into some problems that led me to believe it was not serializing properly.
Dont know, but
> Would a TTimer OnTimer event in the main application thread mess
> with the message pump?
The timer is driven by the message pump and is quite safe, if not
essential in most ICS applications to handle timeouts, lockouts, etc.
Angus
--
To unsubscribe or change your settings for TWSocket mail
I'm eager now to try ICS.
Out of curiosity, is the behavior of the D5 TServerSocket (in non-blocking
mode) the same as ICS? I've used the D5 component in the past and have run
into some problems that led me to believe it was not serializing properly.
Would a TTimer OnTimer event in the main appli
You can remove the offending line and /ADD/ the following two lines at the
beginning of InternalOpenLogFile, just after InternalCloseLogFile:
if (FLogFileOption = lfoOverwrite) and FileExists(FLogFileName) then
DeleteFile(FLogFileName);
This should solve the problem and yet preserve t
Hello Frédéric,
> It seems to work, but it would be interesting to understand why I
> don't get any info at the socket side when I power off the printer for
> example...
This is because the printer does just poweroff. "Disconnecting a TCP
session" means that the disconnecting side will send a pac
