[Customdrawn] Some patches
mschnell at lumino.de
Fri Mar 30 09:36:07 CEST 2012
On 03/30/2012 08:58 AM, Felipe Monteiro de Carvalho wrote:
> Ok, I will apply the new timer but not make it default, because I
> think that the use case of lots of messages going around it a
> critically important use case, much more then precision when there are
> few events. The new timer would negatively affect LazClock heavily for
This is one of the reasons that made me try to test Customdrawn.
I recon that it should be possible to use Customdrawn to create a
project that has no local GUI (e.g.: no user interface at all or working
"remote" by passing the GUI calls and events through a pipe, such as a
Linux Fifo, a Windows messages based mechanism (to have some normal GUI
"remote-control" program communicate with a Daemon / Service), a TCP/IP
port or a serial interface (remote control from a different box). This
also would enable doing long living (i.e. "embedded") CGI projects that
use internal TTimers and allow communication via the WebServer.
To me this sound rather in sync with the effort necessary to do a decent
Android GUI interface (using the Java-based Android libraries) which
also seems to ask for a kind of "remote GUI".
For such purposes the TTimer and the thread communication
(TThread.Synchronize and TApplication.QueueAsyncCall) need to work
without any GUI binding that would provide an event queuing mechanism,
but nonetheless GUI generated events need to be queued to be handled by
the main thread one after the other.
I hope that there will be an (optional) Timer / Event Queue
implementation that allows for all this.
More information about the Customdrawn