I've done this exact sort of thing before, having failed to find a quick
and efficient way to interface my VB programs to pov-ray( i.e. without
rewriting the source code in VC++ to operate as an ocx, which I'm not sure
would be cool with their licensing...)
	And I have to say that although it isn't a perfect solution, calling a
	shell on pov-ray isn't a total pain. Plus you can use the API to catch the
	window handle and send signals that way.  I always just stuck to writing a
	batch file and calling pov-ray with the right command line switches. It
	worked fine for specialized animation work.

	But I also have to agree, an easy ocx patch between vb and povray would be
	super awesome.

On 30-Jun-1998, "DreamChaser" <Dre### [at] spydeenet> wrote:

> Another thought.  Since POV files are just plain text files, you could
> write
> your own editor.  save the file then load and render in POV, or call POV
> (ShellExecute()) with the proper command line switches.  True this is not
> what you (or I) would really want, but if your just learning VB then that
> might be the best route.
>
> DC :)
>
> p.s.  I've worked with VB for a long time and I've just changed over to
> Borlands C++ Builder.  If you are just learning programming, you might
> look
> into that.  BCB is based on the Delphi VCL (Visual Component Library) and
> has done to C++ windows programming what VB did for BASIC windows
> programming.
>
> p.s.s.  I've been playing with the idea of porting POV to BCB and made the
> UI in about 2~3 hours.  I'm looking for the POV source code to see how to
> merge the two.  Any thoughts about new UI options would be appreciated.

Post a reply to this message