> Arno Garrels wrote:
> Actually it's simpler than it sounds, if you do not use your own message
loop but ICS' method MessageLoop, there's nothing to change for OSX. If you
use your own
> message loop a few IFDEF's are required, which isn't a big deal and
something I'll show in a new demo when I h
Arno Garrels wrote:
> Hoby Smith wrote:
>
>> However, being that this thread is in a FireMonkey HD app, I am
>> unsure how to proceed. Do all the threading message pump issues
>> still apply?
>
> Yes. In Windows anyway and in Posix there's Window's messaging
> emulated (as it's needed to not cha
> Yes. In Windows anyway and in Posix there's Window's messaging emulated
(as it's needed to not change ICS' source code too much). In Posix a thread
doesn't have to call GetMessage(),
> PeekMessage() that's the major difference.
> Unfortunately there's not yet a FMX threaded demo available, I'll
Hoby Smith wrote:
> However, being that this thread is in a FireMonkey HD app, I am
> unsure how to proceed. Do all the threading message pump issues
> still apply?
Yes. In Windows anyway and in Posix there's Window's messaging emulated
(as it's needed to not change ICS' source code too much).
Hello.
I am building some test FireMonkey HD apps in Dephi/RAD Studio XE3 using ICS
that I am hoping will eventually build cross platform to Mac. There are two
apps, one is a server and the other a client, and they will exchange some
large amounts of data.
When they are running on the sa
Patrick Wong wrote:
> Dear all,
>
> In my application I am using a TWSocket in a working thread for heavy
> traffic to/from server. Since there is no window in thread the
> TWSocket requires the MessageLoop() to receive events. My approach
> is when there is no data to send the TWSocket keeps to
Dear all,
In my application I am using a TWSocket in a working thread for heavy traffic
to/from server. Since there is no window in thread the TWSocket requires the
MessageLoop() to receive events. My approach is when there is no data to send
the TWSocket keeps to be looped within the Message
