Vadim Sytnikov <syt### [at] rucom> wrote:
> I was not referring to the very possibility, at all. I meant that I needed a
> quiet start

  Is it really that bad that the POV-Ray splash screen shows up *once* at the
start of your program?
  As we can see from Moray, you only need to start POV-Ray once and then use
it for rendering during the whole execution of your program, no matter how
many renders you need.

> (no, not to violate the license! :-), and every time Windows
> version of POV-Ray starts, it grabs focus and does other unwanted (for
> me...) things.

  It doesn't grab focus with Moray.

-- 
plane{-x+y,-1pigment{bozo color_map{[0rgb x][1rgb x+y]}turbulence 1}}
sphere{0,2pigment{rgbt 1}interior{media{emission 1density{spherical
density_map{[0rgb 0][.5rgb<1,.5>][1rgb 1]}turbulence.9}}}scale
<1,1,3>hollow}text{ttf"timrom""Warp".1,0translate<-1,-.1,2>}//  - Warp -

Post a reply to this message

"Ken" <tyl### [at] pacbellnet> wrote:
>
> Well, it seems we have a solution here. You can use the source code to
> compile your own console version. The POV-Team will continue providing
> POV-Ray as they have. When you compile your own console version you
> do so with the full knowledge that you will use if explicitely for your
own
> purposes and will not distribute it publically. I honestly don't see where
the
> problem is.

Sure, there is no problem. I just tried (w/o much luck, as I see, in that no
one got it; my language problem?) to say that *if* there were an official
console version, it would make my life easier. I did not say that since
there are no official Win32 console version, I have a problem... No.

<completely different matter>

It is my understanding that if I ever decide to distribute my programs
(either publicly or just to a selected people; BTW, currently, I distribute
just the results of their work, so to say) altogether with the custom
version of POV-Ray, I have to do the following:
1) make complete sourse code (== all my modifications) of the custom POV-Ray
version publicly available,
2) make sure that each time my software runs POV-Ray, this fact is
prominently presented to the user of said software, by whatever means.
3) include original POV-Ray legal and authorship information.

Current scheme looks like this: when my software runs POV-Ray, respective
message appears on its console. The POV-Ray itself resides in the bin
subfolder, altogether with povlegal.doc and povwhere.txt files. If run by
itself (povray.exe), it displays all the credits and copyright information,
just as an official version does. The version is clearly marked as
"Unofficial Win32 Console (x86)..." etc.

I acknowledge that I'm currently the only user of my custom version of
POV-Ray and that, as soon as I pass it to anyone esle, I will make the
complete source code publicly available.

</completely different matter>

Post a reply to this message

Vadim Sytnikov wrote:

> <completely different matter>
> 
> It is my understanding that if I ever decide to distribute my programs
> (either publicly or just to a selected people; BTW, currently, I distribute
> just the results of their work, so to say) altogether with the custom
> version of POV-Ray, I have to do the following:
> 1) make complete sourse code (== all my modifications) of the custom POV-Ray
> version publicly available,
> 2) make sure that each time my software runs POV-Ray, this fact is
> prominently presented to the user of said software, by whatever means.
> 3) include original POV-Ray legal and authorship information.
> 
> Current scheme looks like this: when my software runs POV-Ray, respective
> message appears on its console. The POV-Ray itself resides in the bin
> subfolder, altogether with povlegal.doc and povwhere.txt files. If run by
> itself (povray.exe), it displays all the credits and copyright information,
> just as an official version does. The version is clearly marked as
> "Unofficial Win32 Console (x86)..." etc.
> 
> I acknowledge that I'm currently the only user of my custom version of
> POV-Ray and that, as soon as I pass it to anyone esle, I will make the
> complete source code publicly available.
> 
> </completely different matter>

That pretty much sums it up. The POV-Team wants you to ensure that anyone
running one of your application in conjunction with POV-Ray is fully aware
that POV-Ray is a separate entity from your application and due credit is
given to the authors of POV-Ray and the POV-Team. We (The TAG and POV-Team)
don't go out of our way to advertise when we catch people distributing
POV-Ray illegally but it happens more often than we would like. There are
commercial programs developed and sold for large amounts of money that
offer "A Photo Realistic Rendering Engine" and the fact that POV-Ray is
used is totally hidden to the purchasers of the program.

-- 
Ken Tyler

Post a reply to this message

On Mon, 3 Mar 2003 02:55:09 +0300, "Vadim Sytnikov" <syt### [at] rucom> wrote:
> Sure, I gave it a try. How it (repeatedly) uses it was what Thorsten has
> suggested (a GUI extension), and I thought I have explained why I cannot use
> that myself.

So this is not enough for you ?

http://throwable.com/dreampeach/download/QuietPOV/

ABX

Post a reply to this message

"ABX" <abx### [at] abxartpl> wrote:
> > ...I thought I have explained why I cannot use
> > that myself.
>
> So this is not enough for you ?
>
> http://throwable.com/dreampeach/download/QuietPOV/

From their docs:
  "There are two parts to QuietPOV. There is the actual QuietPOV GUI
Extension which POV-Ray needs to load, and a command-line executable that
sends POV-Ray commands via the GUI Extension."

Please note the existance of the special command line executable. Seems like
it is a must if you teach the POV-Ray to start quiet.

So the answer is still "no, a GUI extension alone is not enough for me".

Post a reply to this message

Vadim Sytnikov wrote:
> 
> [...]
> 
> So the answer is still "no, a GUI extension alone is not enough for me".

That's not true, get the source code of that tool and have a look at the
file 'QuietPOV.cpp' which implements the console program you mentioned. 
You can implement the same functionality inside your program.

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 28 Feb. 2003 _____./\/^>_*_<^\/\.______

Post a reply to this message

"Warp" <war### [at] tagpovrayorg> wrote:
>
>   Is it really that bad that the POV-Ray splash screen shows up *once*
> at the start of your program?

Yes.

>   It doesn't grab focus with Moray.

It does. Or, as Thorsten would say, "of course it does".

Look, people...

(Well, Warp, I am referring not to you, personally, but to all of you who
"teach" here.)

I am somehow under strong impression that that my "it does" sentence will be
immediatelly replied with "no, sure it does not; you actually did not see
what you saw". I have just re-installed Moray 3.3 specially to test this
particular thing. On the very first run it did grab the focus and even did
not relinquish it. Any other runs (after exiting POV-Ray, but w/o rebooting
Win2000) led to grabbing and immediate releasing the focus to POV-Ray; sort
of a flicker.

What I want to say is that I would not want another reply that insists that
I do not actually need what I need and that I did not see what I actually
saw. Would it actually lead anywhere but to another... err, strong
disagreement? No. Then let's leave it at that.

Post a reply to this message

"Christoph Hormann" <chr### [at] gmxde> wrote:
>
> That's not true, get the source code of that tool and have a look at the
> file 'QuietPOV.cpp' which implements the console program you mentioned.
> You can implement the same functionality inside your program.

Christoph,

I have already implemented all the functionality I needed.

Thank you.

Post a reply to this message

Vadim Sytnikov <syt### [at] rucom> wrote:
>>   It doesn't grab focus with Moray.

> It does. Or, as Thorsten would say, "of course it does".

  Then it has changed since I last used. The last time I used it (well, it
was quite long ago) POV-Ray kept in the background all the time and rendered
the image into the render-window of Moray. Perhaps it has changed for some
odd reason.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

Warp's furious key-hammering produced this:
>>>   It doesn't grab focus with Moray.
>> 
>> It does. Or, as Thorsten would say, "of course it does".
> 
>   Then it has changed since I last used. The last time I used it (well, it
> was quite long ago) POV-Ray kept in the background all the time and rendered
> the image into the render-window of Moray. Perhaps it has changed for some
> odd reason.

Odder still, POV-Ray grabbing focus in Moray, at least for me, seems to happen
only on certain system configuration.  When I used Win2K POV-Ray jumped on top
of Moray when I told it to render (IIRC it didn't do it with material previews,
strangely enough).  However, since I moved up to WinXP it hasn't done that.

I think it jumped in front when I used it in Win95/98, but I don't remember for
sure -- that was many a year ago. ;)

-- 
/*^*/light_source{100*<-5,2,-5>2}#macro I(i,n)#while(strlen(i)>=n)#local A=asc(
substr(i,n,1));#local a=asc(substr(i,n+1,1));cylinder{<div(A,8)-12,mod(A,8)-4,4
><div(a,8)-12,mod(a,8)-4,4>,0.1pigment{rgb z}}#local n=n+2;#end#end I("ScUe[]"1
/*<*/)I("mkmtlttk"1)//@_$#!,:<"Thhis polysig brought to you by Ian Burgmyer :)"

Post a reply to this message