> I tried adding the CustApp unit into uses but it does not help. Of course, the unit only declares TCustomApplication with no instance, which real application must extend and override its virtual methods + declare and initialize its instance. See how Forms unit does it for LCL application.
> In general, is there a need for Application.Processmessages only in a > GUI app There's no message loop in console applications thus Application.ProcessMessages is meaningless there (what would be in the message loop anyway? message to repaint the console? :p). > and if so how can one handle this in classes that need to be > used in both GUI and non-GUI programs? Depends on what the code does. Sometimes it's not possible because the code is tied to GUIism. But in general, use callback method. Should be somewhat equal to having a base class with abstract method, and another two extending it with the abstract method implemented for specific platform / application type. -- View this message in context: http://free-pascal-lazarus.989080.n3.nabble.com/Lazarus-Application-Processmessages-in-console-program-tp4048517p4048518.html Sent from the Free Pascal - Lazarus mailing list archive at Nabble.com. -- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus