> a little help within the program might be usefull. i tried it quickly just
> to see what it looked like. With the gradient feature, i clicked on the
> autofile button, specified a name, and it didn't create the file. but
> strangely, in the recent documents menu or the windows start menu, that
> filename appeared. clicking on it failed to find it though.
>
> i'd go with a more standard File->Save or File->Export method.
>
> also, in the color picker, clicking in the red, green or blue color column
> doesn't move the marker there, only clicking and dragging moves the marker.
>
> and one last think i noticed, with "Add to custom colors" the colors aren't
> preserved after closing and restarting the program.
>
> other than that, nice work. it looks good.

This is just an initial release for now.

I can fix the color picker issue by responding to mouse down events as well
as mouse move events in the slider zone.  I'm going to also add support for
storing custom colors and maybe even the gradient or presets of gradients.
I'm also thinking about adding a preview mechanism for the gradient picker
that could load images under a preview directory and then map the grayscale
values to the color map and also display the opacity as a checkered
background.

When you turn autofile on, you have to click choose gradient and click 'ok'
for it to save it.  I plan on changing this and changing the output format
to be like the maps included with POVRay:  Example

#declare <mapname> = colormap { ... }

This way you can just include it at the top of a file and refer to it by
name.

Also another limitation is that a gradient can have at most
MAX_GRADIENT_ITEMS items since it presently uses an array.  I may later
change it to use a list so it can have more items.

Since you used it, how well does the 'alpha' support work in the gradient
dialog specifically in translating it to the POVRay transmit value?

Post a reply to this message