In article <MPG.18ac6f4e1bd9e05c989720@news.povray.org>, 
sha### [at] hotmailcom says...
> I think this would theoretically resolve the issues in the license as it 
> stands, but I really don't understand how the bloody GUIExt interface 
> works and if those streams even available to the extension (something 
> that would tend to blow a hole in my idea). I don't really want to spend 
> a lot of time trying to figure the interface out if I can't feed those 
> streams through it or this idea has some unintentional defect with regard 
> to the licensing...
> 


Ok.. Maybe bloody was a bad choice of words there. However, this is 
supposed to be an understandable and I assume easy to use interface. The 
problem is that no example exists that really shows what each of the 
functions in it do, there is no documentation in the code that spells 
out, even in a general sense, what its bits are pieces are designed for, 
the only available working examples are A) an incomplete 'example' that 
doesn't do or entirely explain anything, B) a pure console based version 
that lacks most of the key features of the interface I need to use and C) 
the one for Moray, which they don't supply source for and doesn't answer 
my question about what text streams are actually supported. Right now 
this COM bridge is an interesting feature I would like to add to what I 
am doing, not something so critical I plan to spend days rummaging 
through the POVRay source trying to figure out (even if it looks like 
that is the only way I will get any answer).

I need really only two questions answered:

1. Would this design be likely cause a licensing issue.
2. Do the same text streams that show up in Codemax for the rendering 
information also get fed through something in the GUIExt interface?

I have looked at the general code and from what I can tell the answer to 
#2 is likely to be 'no', which would be seriously inconvenient. Then C++ 
gives me a headache to read, so... lol

-- 
void main () {

    call functional_code()
  else
    call crash_windows();
}

Post a reply to this message