On 11/23/04 1:48 PM, "Simon Lord" <[EMAIL PROTECTED]> wrote:
> Yeah, under the 2.5 engine though it still seems to create the "could > not open image" error if I use *empty* or "". Sorry, I neglected to > mention that in my first post. Well, it seems to both do what it's supposed to do (clear out the image) *and* return "could not open image". I think that this is an error. I checked in MC 2.5.1 and it has the same thing, so it's something that should be bugzilla'ed (it shouldn't return an error). Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] _______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
