I am working on some changes to my Isosurface plugin.

A 'Display output' button, which will list all of the options the plugin
outputs to Pov. It will appear in a window like the 'About this plugin'
button. You can look at all of the declares (full length), any options, and
the function statement. Moray's scale, rotate, translate, will only appear
as the word 'Transformations'.

A wireframe detail level. I'm not happy with the current wireframe for the
contained_by sphere. I think 2 or 3 options for wireframes with less detail
can be useful.

I'm currently saving all #declare statements as strings, whether there used
or not. Changing unused #declare statements to something else will hopefully
reduce the file size when saved.

Comments welcome on these changes, or other changes you'd like to see.

Stephen

Post a reply to this message

Hi,
Your plugin is very usefull, and your updates look like a real improvement
for user friendlyness :-)

Now, I often use several similar isosurfaces using the same functions.
POV returns an error message that I may not declare twice the same function.
To fix that issue, I rename my functions for different isosurfaces.
But a "Undefine all declared functions" option check box could be easier
don't you think so?

Or maybe there is a turnaround I didn't think of.

BTW could anybody develop a mesh display (with variable details level
setting) of the isosurface with, maybe a conversion to mesh, usefull for
fast test renders, no?


Cheers
Marc

Post a reply to this message

> Now, I often use several similar isosurfaces using the same functions.
...
> But a "Undefine all declared functions" option
...
Because you can declare more than one function per line and even include
some #if/#else statements, I think this will be to difficult for me to
implement.

>Or maybe there is a turnaround I didn't think of.
One possible workaround is to union your Isosurface object with a CSGcode
object(separate plugin), with the CSGcode listed second in the union. With
the additional lines available used to #undef functions. This should allow
you to duplicate the union(untested).

> BTW could anybody develop a mesh display ...
This will forever remain beyond my abilities.

Stephen

Post a reply to this message

...
> A 'Display output' button, which will list all of the options
...
I like 'List output' better. I've put a partial screen capture in
moray.binaries showing my progress so far.

Stephen

Post a reply to this message

3e5aae10@news.povray.org...
> > Now, I often use several similar isosurfaces using the same functions.
> ...
> > But a "Undefine all declared functions" option
> ...
> Because you can declare more than one function per line and even include
> some #if/#else statements, I think this will be to difficult for me to
> implement.
>
Ok I think I can live without that :)

> >Or maybe there is a turnaround I didn't think of.
> One possible workaround is to union your Isosurface object with a CSGcode
> object(separate plugin), with the CSGcode listed second in the union. With
> the additional lines available used to #undef functions. This should allow
> you to duplicate the union(untested).

oh is it an existing plugin? where is it available?

>
> > BTW could anybody develop a mesh display ...
> This will forever remain beyond my abilities.
>

I wrote "anybody" :-)

Marc

Post a reply to this message

> > One possible workaround is to union your Isosurface object
> > with a CSGcode object(separate plugin)....
>
> oh is it an existing plugin? where is it available?
It can be found at http://ca.geocities.com/morayplugin/
Originally I couldn't find a reason for someone to use the plugin, it never
occurred to me that I might need to #undef a function :-)
I will send the file over to Andre de Leiradella so he can include it with
the other fullmoon plugins.

> > > BTW could anybody develop a mesh display ...
> > This will forever remain beyond my abilities.
> >
>
> I wrote "anybody" :-)
 :-)

You also wrote in moray.binaries.
>Oh I forgot!
>Is it possible to add a Isosurface settings fold button as for many
objects?
>please :-p
>Marc
I'm not sure what the question is.
I think your saying the plugin takes up lots of room, and it's annoying to
continuously click and drag up/down to see all the parts. Unfortunately
Fullmoon doesn't offer a way to collapse some of the controls.
At least I think it's annoying, and I try to make my plugins small.

Stephen

Post a reply to this message

3e5d5574@news.povray.org...
> It can be found at http://ca.geocities.com/morayplugin/

Thank you :-)

> I'm not sure what the question is.
> I think your saying the plugin takes up lots of room, and it's annoying to
> continuously click and drag up/down to see all the parts.

Yes that was the question.

> Unfortunately
> Fullmoon doesn't offer a way to collapse some of the controls.

:-/

> At least I think it's annoying, and I try to make my plugins small.
>
Ok thank you again

Marc

Post a reply to this message

Stephen,
I like your plugin, and it is very useful. Also I think the update is going
to improve it. The 'Display output' will certainly make things easier for
showing what one is doing.
A question: is there a reason (yes, of course there is!! ;-> ) for the
texture being declared separately from the Moray standard declaration? It
does not matter too much, but now there is no way to make de texture 'local'
or 'world' or 'parent'. Again, I can live with this, just wondering.

Thomas

"StephenS" <ssh### [at] echelonca> schreef in bericht
news:3e5998e0@news.povray.org...
> I am working on some changes to my Isosurface plugin.
>
> A 'Display output' button, which will list all of the options the plugin
> outputs to Pov. It will appear in a window like the 'About this plugin'
> button. You can look at all of the declares (full length), any options,
and
> the function statement. Moray's scale, rotate, translate, will only appear
> as the word 'Transformations'.
>
> A wireframe detail level. I'm not happy with the current wireframe for the
> contained_by sphere. I think 2 or 3 options for wireframes with less
detail
> can be useful.
>
> I'm currently saving all #declare statements as strings, whether there
used
> or not. Changing unused #declare statements to something else will
hopefully
> reduce the file size when saved.
>
> Comments welcome on these changes, or other changes you'd like to see.
>
> Stephen
>
>

Post a reply to this message

"Thomas de Groot" <t.d### [at] internlnet> wrote in message
news:3e5f681a@news.povray.org...
...
> I like your plugin, and it is very useful.
...
Thank you :-)

> A question: is there a reason ... for the
> texture being declared separately from the Moray standard declaration?
...
This is a limitation of the Fullmoon Lua scripting plugin, which I used to
make my plugins. Without this added layer of simplification, I my not have
started to write plugins. Someday I would like to use VC++, but not today
:-)

Stephen

Post a reply to this message

"StephenS" <ssh### [at] echelonca> schreef in bericht
news:3e601072@news.povray.org...
>
> "Thomas de Groot" <t.d### [at] internlnet> wrote in message
> news:3e5f681a@news.povray.org...
> > A question: is there a reason ... for the
> > texture being declared separately from the Moray standard declaration?
> ...
> This is a limitation of the Fullmoon Lua scripting plugin, which I used to
> make my plugins. Without this added layer of simplification, I my not have
> started to write plugins. Someday I would like to use VC++, but not today
> :-)
Aah! Thank you! That answers it! Just keep up the good work.
I would like to do some programming again, like in the good old times, but
the clash between many things to do and a chronic lack of time somehow...
Ah, well!

Thomas

Post a reply to this message