On Tue, 24 Apr 2001 15:32:08 +0200, Christoph Hormann wrote:
>I meant it actually returned *before* the render was finished.  Since no
>output is generated anyway this does not make much difference of course.  

Of course it returns before the render is finished.  That, however, is a
Windows issue and not a POV-Ray issue.  If you're using a batch file, 
consider the various options given to you by the "start" command.  If
programming in a more useful language, ponder the ShellExecuteEx function
and how it could be used with WaitForSingleObject to achieve the desired
goal.

-- 
Ron Parker   http://www2.fwi.com/~parkerr/traces.html
My opinions.  Mine.  Not anyone else's.

Post a reply to this message

Christoph Hormann wrote in message <3AE58058.EEC1D897@gmx.de>...
> I meant it actually returned *before* the render was finished.  Since no
> output is generated anyway this does not make much difference of course.


I don't know if it is possible with other windows but in NT 4 there is command
START with optional parameter /WAIT. It waits until task not finish.

start /wait povray.exe

I don't know what about return codes from runing

btw: command START can also set priority of task

ABX

Post a reply to this message

Ron Parker wrote:
> 
> You should investigate the available command line options more thoroughly.
> [...]
> You should investigate the available command line options more thoroughly.
> 

Perhaps i should emphasize that i wasn't complaining, i just want to
mention that WinPov is not an universal substitute for a command line
version.  The additional options do not really help.

Most editors, probably including emacs, have functions for invoking
external programs like compilers and also include analysis of error
output, but they are designed for command line programs and therefore will
not work with WinPov that easily.  Of course one could redirect the output
to a text file and print it out again in a batch afterwards, but i really
don't thing this is a really acceptable solution also because of the other
disadvantages i mentioned.  

Christoph

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message

Wlodzimierz ABX Skiba wrote:
> 
> I don't know if it is possible with other windows but in NT 4 there is command
> START with optional parameter /WAIT. It waits until task not finish.
> 
> start /wait povray.exe
> 
> I don't know what about return codes from runing
> 
> btw: command START can also set priority of task
> 
> ABX

I know about that although i had forgotten it for the moment. Thanks for
mentioning it.  Anyway the most important problem stays, i.e. the program
takes at least some seconds to load and therefore it's not really useful
to start it again every time.  

As already mentioned a GUI Extension offers very nice possibilities for
this (you could render scenes in a already running version of WinPov this
way). I did not have luck getting it work in the past, but i did not try
very hard anyway...  

Christoph

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message

Christoph Hormann wrote in message <3AE58C91.F64F9AAF@gmx.de>...
> most important problem stays, i.e. the program
> takes at least some seconds to load and therefore it's not really useful
> to start it again every time.

if you know that you render very often than you can run one winpov at start of
system and every next run use the same loaded code block and only allocate
memory for data - it's rule of windows I think

ABX

Post a reply to this message

In article <3AE589A1.83D6CE1E@gmx.de> , Christoph Hormann 
<chr### [at] gmxde>  wrote:

>  Of course one could redirect the output
> to a text file and print it out again in a batch afterwards

You can also redirect to stdout, but I am not sure if this works in windows
programs.


____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Christoph Hormann wrote in message <3AE56CB8.8A9ACC75@gmx.de>...
> Probably not a very good solution.  I tried it with other programs and
> found that it:
>
> - takes quite a long time to load
> - does not print out anything (error info, stats) that can be used by the
> invoking program
> - does not return as you would expect from a console program
> - does not work at all if 'keep single instance' is activated.

As mentioned before not everything is true, but I must admit that I use your
CygWin compilation for one reason. It not changes enviroment I think. I mean
that I can take it on any disk to anywhere and not worry that I change something
(registers). I mean that console compilation is clean for system and very
helpful for handy distributed rendering :-)

ABX

Post a reply to this message

Wlodzimierz ABX Skiba wrote:
> 
> if you know that you render very often than you can run one winpov at start of
> system and every next run use the same loaded code block and only allocate
> memory for data - it's rule of windows I think
> 

I think WinPov starts somewhat faster if it was already started before,
but the difference is quite marginal and i never came below 3 seconds
here.  

Christoph

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message

Wlodzimierz ABX Skiba wrote:
> 
> As mentioned before not everything is true, but I must admit that I use your
> CygWin compilation for one reason. It not changes enviroment I think. I mean
> that I can take it on any disk to anywhere and not worry that I change something
> (registers). I mean that console compilation is clean for system and very
> helpful for handy distributed rendering :-)
> 

The main problem is that it's actually quite a lot slower, therefore a
different solution (like with Gui Extension) would be nice.  

Christoph

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message

Christoph Hormann wrote in message <3AE69C34.C8C8A901@gmx.de>...
> The main problem is that it's actually quite a lot slower

I see this waiting second day for my
rendered sprout box with your corrections :-(

ABX

Post a reply to this message