Jeff- You're running dxexec without the dx script and dxworkerscript to set up the environment. dxexec can't find the macro (dxfSaveCurrentImage) because you haven't set DXROOT. set DXROOT and I think your warning will go away.
As for ReadImage: Thanks for tracking this down. Change the IM api? aaargh. I looked for a benign call with a predictable number of arguments to detect the IM shared lib version at runtime prior to making the ReadImage call. Couldn't find one offhand. Any suggestions? I think I'll end up updating our code for the new IM api-- and hope the api stabilizes. Have a good weekend, all. Pete Jeff Braun wrote: > I guess I should followup on a few things before the long weekend. When I > run with the debugger, I do not get a disconnect, but rather just an error > message in the Message window: > > 0: ERROR: dxfSaveCurrentImage: function does not exist > 0: WARNING: Function return values are ignored: dxfSaveCurrentImage > > I see that dxfSaveCurrentImage is a macro, what do I need to do run dbx so > I can use it. > > When I run without dbx dxfSaveCurrentImage seams to call WriteImage: > > 0: WARNING: input contains no fields or only empty fields > 0: The specified extension or format was unrecognized or unsupported, > tried to use: > 0: gif > 0: if format specified is *exactly* 'Image Magick supported format' then > perhaps the file extension is faulty. > 0: ERROR: 89::/dxfSaveCurrentImage:0/WriteImage:1: Bad parameter: > invalid extension, format, or unsupported by ImageMagick > > I can save a miff with the miff pulldown option, but if I use the > ImageMagick pulldown option, then I get a similar warning/error as for a > gif image above. > > ---------------------------------------------------------------------- > I am recompiling dx4.1.0 using the new ImageMagick package, where I did > get one error message in src/exec/dxmods: > > _im_image.c: In function `write_im': > _im_image.c:211: too few arguments to function `ReadImage' > > The ReadImage function now requires 2 args, so I passed NULL for the 2nd > arg just to see what happens. I also noticed that were a variety of other > changes in image.h and other header files. Such as WriteGIFImage and > WriteMIFFImage are no longer declared in image.h. > > I guess the solution for now might be to stick with ImageMagick 5.1.1. > > Jeff > > ---------------------------------------------------------------------- > Jeff Braun Geophysics Dept. > mailto: [EMAIL PROTECTED] Montana Tech > (406) 496-4206 1300 W. Park St. > Butte, MT 59701
