> > > > The synchronize calls shouldn't be placed inside your TThreadedProcess > > code... they should be used in the main application thread to provide > > mutual exclusion for the shared visual components. > > It's the other way round, at least in delphi: you call synchronize from > a thread when you want the method executed in the context of the main > thread. That is correct, I know this much at least :) after all how can you synchronize from the main thread it doesn´t know what the other thread is doing. Anyway I think the problem is right at the design level, the right way I think would be to create a tthread descendent in a unit, with an extra property FCommandLine which can be overwritten at instantiation time.
Pretty much what I had, but it should NOT be instantiated in the program. Instead the same unit should contain a tcomponent descendent which instantiates the tthread descendent, takes its values from poperties to pass on to the ththread descendent (which itself is a property) and THEN the thread can synchronize with a property of the tcomponent for output ? Am I getting closer you think ? A.J. -- "80% Of a hardware engineer's job is application of the uncertainty principle. 80% of a software engineer's job is pretending this isn't so." A.J. Venter Chief Software Architect OpenLab International http://www.getopenlab.com | +27 82 726 5103 (South Africa) http://www.silentcoder.co.za | +55 118 162 2079 (Brazil) _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
