Eric Fleming Bonilha wrote:
> That is good too, we just need a method to increase the value, 200 is
> good ;)
I just checked in a change, please test it and let me know how it works
for you.
Log:
Added TIcsWndHandlerPool.SetWndHandlerMaxMsgIDs() to provide an option to
change default maximum
That won't work since TIcsWndHandler declares a static array with
length WH_MAX_MSG.
Instead I suggest that TIcsWndHandlerPool gets a public, thread-safe
method which checks whether the value can be changed and would raise
an exception if not. This method would succeed only if the pool
was empty (
Eric Fleming Bonilha wrote:
> I would suggest the changing of constant WH_MAX_MSG in
> OverbyteIcsWndControl.pas to a global variable to which we can change
> on our software, without changing ICS code.
That won't work since TIcsWndHandler declares a static array with
length WH_MAX_MSG.
Instead
Hello
I would suggest the changing of constant WH_MAX_MSG in
OverbyteIcsWndControl.pas to a global variable to which we can change on our
software, without changing ICS code.
Doing this will allow us to control the amount of shared resources per handle,
giving the ability to create more socket
