Kenneth <kdw### [at] earthlinknet> wrote:
> Problem #1: Using POV for Windows (which has .bmp as a default output
> format), I can't specify  image_map{bmp "my_image.bmp"}  because it
> generates an error mesage: "undeclared identifier 'bmp' found."

  That's because there's no 'bmp' identifier. Read the documentation more
carefully. (In this case the identifier is 'sys'.)

> So I have
> to specify it this way:  image_map {"my_image.bmp"}. Rather odd.

  Well, if it works, what's the problem?

-- 
                                                          - Warp

Post a reply to this message

Warp <war### [at] tagpovrayorg> wrote:
> Kenneth <kdw### [at] earthlinknet> wrote:
> > Problem #1: Using POV for Windows (which has .bmp as a default output
> > format), I can't specify  image_map{bmp "my_image.bmp"}  because it
> > generates an error mesage: "undeclared identifier 'bmp' found."
>
>   That's because there's no 'bmp' identifier. Read the documentation more
> carefully. (In this case the identifier is 'sys'.)
>
> > So I have
> > to specify it this way:  image_map {"my_image.bmp"}. Rather odd.
>
>   Well, if it works, what's the problem?

Well, it goes against what the docs says about having to specify the image
file type before the "my_image.bmp" phrase. I don't see any caveat or
exception mentioned there, so perhaps there should be one...OR an actual
bmp identifier (which would be more logical and self-consistent than
leaving it out altogether or using "sys".)

Ken

Post a reply to this message

"Kenneth" <kdw### [at] earthlinknet> wrote:


> Well, it goes against what the docs says about having to specify the image
> file type before the "my_image.bmp" phrase. I don't see any caveat or
> exception mentioned there...

My apologies; that's incorrect. The POV docs DO clearly state that including
the image file type before "my_image.etc" IS optional, depending on other
factors. So in my case, "my_image.bmp" is perfectly reasonable.

Ken

Post a reply to this message