I have been experimenting with the GUIDEMO extension which is contained
in the POV source archive. I am using Borland C++ 5.01a (or b?). The
demo extension compiles fine and I have made the requisite changes to
the source to prevent errors. However, after adding the appropriate line
to the pvengine.ini file nothing happens - not even an error dialog pops
up. I tried changing the name of the extension as shown in the .ini file
to an illegal name, and when I bring up POV the same thing happens, i.e.
nothing. I just get POV-Ray, same as always, with nothing extraordinary
in the GUI Extensions menu (in fact, the grayed out item says: No GUI
Extensions Loaded").

It appears, somehow, that the GUIExtensions line is not being read, or
it is being disregarded:

[GUIExtensions]
UseExtensions=1
ExtDll16=h:\POVRAY\bin\guidemo.pge

I would think that if I changed the name of the extension above to
"guifake.pge" I would get some kind of error like "No such extension".

Has anyone else run into this?

Jon Berndt

Post a reply to this message

"Jon S. Berndt" <jsb### [at] hal-pcorg> wrote:

>I have been experimenting with the GUIDEMO extension which is contained
>in the POV source archive. I am using Borland C++ 5.01a (or b?). The
>demo extension compiles fine and I have made the requisite changes to
>the source to prevent errors. However, after adding the appropriate line
>to the pvengine.ini file nothing happens - not even an error dialog pops
>up. I tried changing the name of the extension as shown in the .ini file
>to an illegal name, and when I bring up POV the same thing happens, i.e.
>nothing. I just get POV-Ray, same as always, with nothing extraordinary
>in the GUI Extensions menu (in fact, the grayed out item says: No GUI
>Extensions Loaded").
>
>It appears, somehow, that the GUIExtensions line is not being read, or
>it is being disregarded:
>
>[GUIExtensions]
>UseExtensions=1
>ExtDll16=h:\POVRAY\bin\guidemo.pge
>
>I would think that if I changed the name of the extension above to
>"guifake.pge" I would get some kind of error like "No such extension".

I can't say why this would be the case. Extensions do work (I tested one for
someone else only a few weeks ago). Try turning on debug (use pvengine.exe
/debug and look for c:\povray.dbg after pvengine has exited.)

If this still doesn't help, then compile the povray for windows source and step
through the initialisation code (LoadGUIExtensions () in PVGUIEXT.C).

If there turns out to be enough interest in GUI extensions I will establish a
group for it.

-- Chris

Post a reply to this message

povray.org admin team wrote in message <346fb646.2807927@news.povray.org>...

>If there turns out to be enough interest in GUI extensions I will establish
a
>group for it.


May I say, yes, there is? Also, yes. And, again, yes.

--Chris

p.s. Yes.

Post a reply to this message

>May I say, yes, there is? Also, yes. And, again, yes.

yeah, ok, we'll see how this one goes. povray.windows.gui-extensions.

-- Chris

Post a reply to this message

povray.org admin team wrote:
> 
> >May I say, yes, there is? Also, yes. And, again, yes.
> 
> yeah, ok, we'll see how this one goes. povray.windows.gui-extensions.
> 
> -- Chris


Great! Can you move the most recent relevant messages to this new
newsgroup?

Jon

Post a reply to this message

Might I recommend a more general newsgroup for compiling/customizing pov,
i.e. povray.programming or something similar.  That would route some of the
traffic about "How do I compile on a -----?" away from CGRR, and would also
provide a forum for people writing patches, extensions, or even utilities.
My guess is that the GUI extension hype will burn out after a while, but
people will always be interested in customizing pov in some way.

Just my 2 cents...

Ken

povray.org admin team wrote in message <346edf46.1641330@news.povray.org>...
>>May I say, yes, there is? Also, yes. And, again, yes.
>
>yeah, ok, we'll see how this one goes. povray.windows.gui-extensions.
>
>-- Chris

Post a reply to this message

povray.org admin team wrote:
> 
> I can't say why this would be the case. Extensions do work (I tested one for
> someone else only a few weeks ago). Try turning on debug (use pvengine.exe
> /debug and look for c:\povray.dbg after pvengine has exited.)

I wondered if there was a way to do this - turning on debug.
 
> If this still doesn't help, then compile the povray for windows source and step
> through the initialisation code (LoadGUIExtensions () in PVGUIEXT.C).

I have taken this route this morning. I am getting an error when I get
to functions.h, from "atmosph.c".  Borland says:

--- code function.h ---
#ifndef RWSTD_NO_NAMESPACE
namespace std {                     <-------- declaration syntax error
#endif
--- end code function.h ---

and:

--- code iostream.h ---
#ifndef __cplusplus
#error Must use C++ for the type iostream.    <-------- Error directive
#endif
--- end code iostream.h --- 

the full error for the above code snippet is: "Error directive: Must use
C++ for the type iostream."

So, I cannot compile the pvengine.lib. I can compile the windows GUI for
POV.

Any suggestions?

> If there turns out to be enough interest in GUI extensions I will establish a
> group for it.
> 

This is a great idea. It might be better to add a group for
povray.programming, though, to encompass building/customizing the front
end, as well ...

Thanks,

Jon Berndt

Post a reply to this message

"Jon S. Berndt" <jsb### [at] hal-pcorg> wrote:

>I have taken this route this morning. I am getting an error when I get
>to functions.h, from "atmosph.c".  Borland says:
>
>--- code function.h ---
>#ifndef RWSTD_NO_NAMESPACE
>namespace std {                     <-------- declaration syntax error
>#endif
>--- end code function.h ---

That can't be part of our code, since it's all C. The above is C++ ... I
presume it's a borland include file of some sort. I can't explain why it would
be happening to you ; it compiles fine for me with Borland C++ v5.01.

-- Chris

Post a reply to this message

povray.org admin team wrote:
> 
> "Jon S. Berndt" <jsb### [at] hal-pcorg> wrote:
> 
> >I have taken this route this morning. I am getting an error when I get
> >to functions.h, from "atmosph.c".  Borland says:
> >
> >--- code function.h ---
> >#ifndef RWSTD_NO_NAMESPACE
> >namespace std {                     <-------- declaration syntax error
> >#endif
> >--- end code function.h ---
> 
> That can't be part of our code, since it's all C. The above is C++ ... I
> presume it's a borland include file of some sort. I can't explain why it would
> be happening to you ; it compiles fine for me with Borland C++ v5.01.
> 
> -- Chris

Yes, it's rather bizarre, and incredibly frustrating. And you are right,
it's not POV code, of course. I think maybe it has to be my
configuration, or options, or something. I think I may download the
source archive again and start from scratch.

Jon

Post a reply to this message

povray.org admin team wrote:
> 
> "Jon S. Berndt" <jsb### [at] hal-pcorg> wrote:
> 
> >I have taken this route this morning. I am getting an error when I get
> >to functions.h, from "atmosph.c".  Borland says:
> >
> >--- code function.h ---
> >#ifndef RWSTD_NO_NAMESPACE
> >namespace std {                     <-------- declaration syntax error
> >#endif
> >--- end code function.h ---
> 
> That can't be part of our code, since it's all C. The above is C++ ... I
> presume it's a borland include file of some sort. I can't explain why it would
> be happening to you ; it compiles fine for me with Borland C++ v5.01.
> 
> -- Chris

Well, I don't know what happened, but the thing all compiles just fine,
now. I unzipped the source archive again. Something must've gotten hosed
somehow when I unzipped the archive the first time.

jb

Post a reply to this message