Just wanted to add another version of what can kill Active4D
housekeeper.
For some reason Housekeeper does not like to find the following type
code in a library :-)
$PODetail{"NailHeadTrim"} := choose([PO]a80_NailHeadTrimLocation #
"";"yes";"no")
<<<<<<< .mine
$PODetail{"cord_location"} := [PO]a80_Location1 //[PO]
a80_CordLocation // Remove the ìmust enter one trim type direction
=======
$PODetail{"cord_location"} := [PO]a80_Location1 // Remove the
ìmust enter one trim typeî direction
>>>>>>> .r536
The GUI SVN tool the developer I am working is using apparently did
not report a conflict. When nothing worked with my last update, I
just knew it had to be housekeeping crashing - and I don't blame it
for doing so.
I'd bet the other post from last week on A4D Init taking a long is
also related to screwed up library files.
Steve Alex
On Aug 22, 2007, at 2:37 PM, Michael Check wrote:
We found the issue. Thanks Steve. It was multiple issues with
libraries.
Here's what we found.
* The sites directory (where we strore all the virtual sites) had
._*.a4l files on it from temp files used by textmate.
* The bugger of a problem was that we found a blank file named the
same as a fusebox circuit. It was not even in the main directory of
the circuit, it was lower. A4D reported no errors but was hanging on
server start mostly (as far as we can tell) because of that blank...
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
