On 20.06.10 01:29, SharkD wrote:
> If you search for tasks by SharkD at the bug tracker you'll see a bunch
> of feature request I've made.
>
> http://bugs.povray.org/
>
> Here's a list if you don't want to do the search:
>
> Master scene unit system variable

This feature was already discussed before - and rejected. POV-ray is a 
unit-less system by design.

> Set and get font metrics

You cannot set them because there is nothing to set in a finished font. You 
can only set font metrics in a font editor. If you want to apply effects to 
text objects, you can transform individual characters with a macro. Getting 
the essential font metrics is already possible with clever use of the 
min_extent and max_extent functions.

> Table of Contents in each page of the docs

Already there, supplied by the system in Windows help docs (given you report 
for Windows). You can also use the PDF docs, which have this, as do the Mac 
help docs.

> More library paths, wildcards

There was information missing in your feature request. Please add it there.

> Explicit #RETURN statement inside macros

You are misunderstanding that macros are not functions. There is no such 
thing as a return from a macro.

> Mixed-type arrays

Already possible.

> Ability to change the order of editor tabs by dragging them

This is Windows only, I suppose.

> Native support for mesh-based surface approximations

You can already do this with a macro. Native support would have no benefit - 
the probable assumption that a high quality mesh would be faster to generate 
and then render compared to a native object (i.e. an isosurface) is incorrect.

> Right-click menu when clicking on editor tab

On Windows, I guess?

> atand function

This is the degree based version of atan. Use the radians and degrees functions.

	Thorsten

Post a reply to this message