Here's an odd one.
In the OutKafelibs package, there is a TThread descendent (among a bunch
of other classes). In previous versions of OutKafe I was calling
TThread.Create repeatedly whenever I had to run a plugin - suffice to
say I found this hugely unclean (tthread.free doesn't have enough
guarantees) so I changed it to use and then continue to REUSE just one
thread.
This meant I had to go put TThread.Create somewhere each OutKafe program
were bound to run it before the first event could be triggered. The
logical place was inside the database creation code.
Chaching -worked like a charm... until now that is.
Suddenly whenever I install this package (set as a runtime+designtime
package) into the IDE the IDE crashes complaining of threading being
initialised BEFORE cthreads. But the dbconnect method SHOULD only be
called by apps using the unit - not by the IDE... why on earth would the
IDE crash then ?
I tried sticking cthreads in the unit and a bunch of other stuff,
nothing works. What DID let me go on, was to change the package to
runtime only, now the apps compile and run, and so does the IDE (with
the package not installed). But this is FAR from ideal - the package
SHOULD be installable. What could cause the IDE to try and create the
thread on startup ?
A.J.
begin:vcard
fn:AJ Venter
n:Venter;AJ
org:Global Pact Trading Pty. Ltd.;OutKast Solutions
email;internet:[EMAIL PROTECTED]
title:Director of Product Development
tel;work:+27 21 554 5059
tel;fax:+27 21 413 2800
tel;cell:+27 83 455 9978
url:http://www.outkastsolutions.co.za
version:2.1
end:vcard
