> Perhaps this should be brought into the core? Are you using the correct Fourq with 2.2? You should have checked out Fourq with tag "b122-beta1" from CVS to go with 2.2.
The problem seems to be in Fourq. Changing the data type in farcry_core would only be treating the sympton. I'll see if I can replicate the problem on my end. ~tom --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
