 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 7 Aug 2003 13:16:35 -0700, Patrick Elliott <sha### [at] hotmail com>
wrote:
> In article <7ni4jvgp2qkstm76cg77a7u5v9tc5kn1d6@4ax.com>, abx### [at] abxartpl
> says...
> > I don't see what is advantage of that plugin over customizable Insert
> > Menu with prerendered images ?
> You mean besides the fact that there is an internal limit on the number
> of items in this menu
What limit? I just looked into BuildDirList function in codemax code and do
not see any hardcoded limit.
> that the last batch I added suddenly caused
> POV-Ray to show menu images on menus 'other' than the insert menu as a
> side effect?
Can you write me more about it?
Have you already reported your problems somewhere ?
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ABX wrote:
> On Thu, 7 Aug 2003 13:16:35 -0700, Patrick Elliott <sha### [at] hotmailcom>
> wrote:
>
>>In article <7ni4jvgp2qkstm76cg77a7u5v9tc5kn1d6@4ax.com>, abx### [at] abxartpl
>>says...
>>
>>>I don't see what is advantage of that plugin over customizable Insert
>>>Menu with prerendered images ?
>>
>>You mean besides the fact that there is an internal limit on the number
>>of items in this menu
>
>
> What limit? I just looked into BuildDirList function in codemax code and do
> not see any hardcoded limit.
>
>
>>that the last batch I added suddenly caused
>>POV-Ray to show menu images on menus 'other' than the insert menu as a
>>side effect?
>
>
> Can you write me more about it?
>
> Have you already reported your problems somewhere ?
>
> ABX
I mentioned this a while back (a couple of months perhaps, but a search
of news.povray.org doesn't reveal the message) and didn't see a response
that addressed a solution. This also was brought up by Thomas Eicher on
10 Sept, 2002. It shows up when adding a couple of Insert menu add-ons
("Basic templates" by Friedrich Lohmueller and "IsoCSG include file" by
a person whose name I don't have access to at this time).
Two problems show up:
1) Past a certain point in the Insert menu, nothing is inserted in the
file being edited. With both add-ons installed, Shapes/quadric will
insert text, but Shapes/quartic will not. This breakpoint changes
depending on which add-ons are present, and what position they are
placed in the menu.
2) Previews show up in strange places. With the above mentioned add-ons
installed, I see previews under various items in the Render menu (for
example "Select File and Render" and "Run Demo"). They show up all of
the way through to "Help/About POV-Ray for Windows...".
Let me know if you need any additional info.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3f33cfb4$1@news.povray.org>, tim### [at] netscapenet
says...
> Two problems show up:
> 1) Past a certain point in the Insert menu, nothing is inserted in the
> file being edited. With both add-ons installed, Shapes/quadric will
> insert text, but Shapes/quartic will not. This breakpoint changes
> depending on which add-ons are present, and what position they are
> placed in the menu.
> 2) Previews show up in strange places. With the above mentioned add-ons
> installed, I see previews under various items in the Render menu (for
> example "Select File and Render" and "Run Demo"). They show up all of
> the way through to "Help/About POV-Ray for Windows...".
>
> Let me know if you need any additional info.
>
>
Exactly. I have the IsoCSG one and the scene templates menus, but as far
as I know I haven't run into item 1 above. However, I do suffer from item
2. On mine I am get the following quirks:
Menu Image
---- -----
Render - Edit Settings CSG Operations - Intersection
Render - Start Render Patterns 1 - Cylindrical
Render - File Queue Patterns 1 - Brick
Render - Animation - No Shell.. IsoCSG include file - iso_bcsg.inc
- shape macros - IC_BSuperellipsoid
Options - Other Settings
- Show Tips of the Day IsoCSG include file - iso_chars.inc
- IC_Text()
Options - Other Settings
- Show Next Tip Pattern/Texture Attributes
- Wave form attribute
Options - Render Window
- Force 8-bit display Patterns 1 - function
Options - Render Window
- Close Transformations - Rotate
Options - Render Window
- Keep Above Main IsoCSG include file - iso-csg.inc
- shape macros - IC_Box()
Options - Message Window
- Select Plain Background Transformation - Translate
Options - Message Window
- Text Font IsoCSG include file - iso-csg.inc
- CSG macros - IC_Difference4()
Options - Message Window
- Text Color IsoCSG include file - iso-csg.inc
- CSG macros - IC_Merge2()
Options - Message Window
- Choose Background - Browse IsoCSG include file - iso-csg.inc
- IC_Displace()
Help - Bug Reporting Patterns 1 - Slope
Help - Show Tip Pattern/Texture Attributes
- Wave form attribute
Help - About... Patterns 2 - Leopard
It may help to know if this is common to all cases of having those menu
extensions installed. I think this started happening right after I
installed the CSG ones, but before adding the Basic scene template one,
so the CSG by itself may somehow be doing it. It is definitely odd and I
don't trust the menu at all because of it.
--
void main () {
call functional_code()
else
call crash_windows();
}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3F325217.CC7B3A90@pacbell.net>, tyl### [at] pacbellnet says...
>
>
> Patrick wrote:
> >
> > Hello,
> > I used Pov-Ray a few years ago when designing furniture pieces. At the
> > time there was a brilliant little plugin that visually showed all the
> > textures in Pov-ray plus a few more. Metal, Stones etc. It was very
> > small and worked perfectly. You could visually browse the
> > textures/finishes and then double click the one you wanted and it would
> > automatically insert the declaration. Unfortunately with non-use and new
> > PC's etc, I have lost it. I wonder if anyone knows what/where it is? For
> > someone who is trying to use Pov-ray for making 3d designs a little more
> > realistic but does not want to get into creating whole new textures it
> > was invaluable. If anyone can help, it would be appreciated.
>
> TextureVeiw?
>
> http://www.friedemann-schmidt.com/software/index.html
>
>
Hmm. The plugin won't work on my copy of 3.5 for some odd reason. It will
load POV-Ray and apparently does something.. But there is no rendering,
it just dims the 'Render' button and the after a bit times out or
something and goes back to normal, with no image created for the texture.
Needless to say this kind of defeats the purpose of the program. :p
Does anyone else have this issue?
--
void main () {
call functional_code()
else
call crash_windows();
}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 08 Aug 2003 10:28:35 -0600, Tim Riley <tim### [at] netscapenet>
wrote:
> Let me know if you need any additional info.
I would need some screenshots and your system specification. IIRC Insert Menu
is handled by CodeMax library and I think debugging and recompiling it is much
more complicated than povray sources but who knows...
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Patrick Elliott" <sha### [at] hotmailcom> wrote in message
news:MPG.199df9cf9da2704989856@news.povray.org...
> In article <3F325217.CC7B3A90@pacbell.net>, tyl### [at] pacbellnet
says...
> Hmm. The plugin won't work on my copy of 3.5 for some odd reason. It
will
> load POV-Ray and apparently does something.. But there is no
rendering,
> it just dims the 'Render' button and the after a bit times out or
> something and goes back to normal, with no image created for the
texture.
> Needless to say this kind of defeats the purpose of the program. :p
>
> Does anyone else have this issue?
Yep, me Patrick. Is it supposed to render the images though? Or
is there something we're both missing? If we have to render the
images, how long will it take? I have something like 550 textures on
my PC.
~Steve~
>
> --
> void main () {
> call functional_code()
> else
> call crash_windows();
> }
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3f37d540@news.povray.org>, dot### [at] dotcom says...
>
> "Patrick Elliott" <sha### [at] hotmailcom> wrote in message
> news:MPG.199df9cf9da2704989856@news.povray.org...
> > In article <3F325217.CC7B3A90@pacbell.net>, tyl### [at] pacbellnet
> says...
>
> > Hmm. The plugin won't work on my copy of 3.5 for some odd reason. It
> will
> > load POV-Ray and apparently does something.. But there is no
> rendering,
> > it just dims the 'Render' button and the after a bit times out or
> > something and goes back to normal, with no image created for the
> texture.
> > Needless to say this kind of defeats the purpose of the program. :p
> >
> > Does anyone else have this issue?
>
> Yep, me Patrick. Is it supposed to render the images though? Or
> is there something we're both missing? If we have to render the
> images, how long will it take? I have something like 550 textures on
> my PC.
>
> ~Steve~
It is supposed to render which ever ones you have selected in order to
generate its internal thumbnail list. It uses some sort of
special database to store this stuff, so I don't think you can simply
take the needed POV file, render it and then try to tell the texture
viewer to import that image. Instead it appears that it is supposed to
work like the preview function that Moray has for textures. Otherwise,
there is really no point at all for it to use a .pge to link the two
together. After all, it can't directly import the text for the texture
anyway, you have to cut and paste it.
Something must have inadvertently been changed in POV-Ray 3.5 that
interferes with this plugin talking to POV-Ray correctly. :( I do
remember it worked right using 3.1 back when I had both programs
installed on my old 486. I 'could' try setting it to use the version of
3.1 I still have installed, but there are new things in 3.5 that you
still couldn't render a thumbnail for in 3.1. :p
Hmm. Trying to remember, was there a source code file for the viewer in
the site? Maybe someone could track down the issue and fix it if so, but
since my eyes cross every time I look at the plugin interface code, I
would prefer it to be someone that knows what they are doing. ;) lol
--
void main () {
call functional_code()
else
call crash_windows();
}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Patrick Elliott wrote:
> Hmm. Trying to remember, was there a source code file for the viewer in
> the site? Maybe someone could track down the issue and fix it if so, but
> since my eyes cross every time I look at the plugin interface code, I
> would prefer it to be someone that knows what they are doing. ;) lol
You could always try contacting the author of the program :)
mailto:web### [at] friedemann-schmidtcom
I am pretty sure that his last update was for POV-Ray v3.1g and he may not
have gotten around to adapting it to v3.5.
--
Ken Tyler
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Just tested it. 3.1g renders the thumbnail correctly. So something got
changed in 3.5 or something that stops this from working right... This is
not good imho, since the plugin stuff is complicated enough to figure out
with minimal examples, without it turning out that in some cases it may
no longer even work at all. :( Of course it is possible that something in
the texture viewer is at fault, but since it appears to suffer from what
you would normally expect if a COM interface hung and then timed out,
this seems to me unlikely.
--
void main () {
call functional_code()
else
call crash_windows();
}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3F3845CC.B20545F0@pacbell.net>, tyl### [at] pacbellnet says...
>
>
> Patrick Elliott wrote:
>
> > Hmm. Trying to remember, was there a source code file for the viewer in
> > the site? Maybe someone could track down the issue and fix it if so, but
> > since my eyes cross every time I look at the plugin interface code, I
> > would prefer it to be someone that knows what they are doing. ;) lol
>
> You could always try contacting the author of the program :)
> mailto:web### [at] friedemann-schmidtcom
>
> I am pretty sure that his last update was for POV-Ray v3.1g and he may not
> have gotten around to adapting it to v3.5.
>
>
True enough, but as far as I was aware, there where no changes to the
code involving the plugins in 3.5, so it 'should' work anyway. Otherwise
older versions of Moray, which use much the same interface, would stop
working right as well. It seems really odd, but I guess contacting him is
probably best.
--
void main () {
call functional_code()
else
call crash_windows();
}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
