 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Later today (Sunday 23 August), POV-Ray for Windows v3.1 beta 6 will be made
available. Other versions will be posted on the web site as and when they
become available. Full release notes will be provided with the beta. The
changes to POVWIN itself are extensive and will be listed in this newsgroup to
allow users to decide whether or not to download it.
Here is a short extract (which may change before the actual release).
Quick Summary:
o Added new editor.
o Added rubberband mode to render window for selection of render region.
o Added auto-load of file if there's a parse error (goes to line and col).
o Modified the way the insert menu works. It's now like the 'Start Menu'.
o Removed a bunch of stuff that was a legacy of our (now gone) Win32s mode.
o The editor is extensively customisable. It utilises syntax highlighting and
understands .POV and .INC files as being in POV syntax. You can change the
colour settings used from the properties dialog (ALT-ENTER). It also has
built-in syntax highlighting for C, C++, Java, Basic, Pascal and SQL.
o Here's a quick editor feature summary. Please inspect the editor menus to
gain a better understanding of its available features, until such time as
the new docs are written.
o Syntax highlighting.
o Keystroke macros. These are preserved across sessions.
o Optional auto-save which, if turned on, saves changed files periodically.
o Brace matching is available (cursor must be on a brace when you do it).
o Block indent/undent
o Tabify/untabify
o Customisable colours.
o Most key bindings are customisable (not all, just most).
o Smart case preservation in replace operations.
o Up to 10 bookmarks.
o Optional auto-reload of changed files (not yet implemented).
o Multiple views of the one file (via splits).
o OLE drag and drop between the editor and other programs.
o Optional smooth-scrolling.
o Intellimouse support.
o Column selection (control-leftbutton and drag).
o Up to 32 edit sessions.
o MRU list also tracks the line, column, language, tab and indent settings.
Renderer bugs fixed since beta.5
Made density{color COLOR} legal mostly for use in density_map
Made pigment{average color_map{}} illegal
Fixed old bezier type 0 bug
Eliminated negative strength blobs from bounding slab calculation
Fixed hfield divide by zero bug on some platforms which didn't trap
Added some missing identifier types as macro parameters
Fixed mosaic preview overflow on odd size images
Implemented material{} statement.
MATERIAL:
material{[MATERIAL_IDENTIFIER][MATERIAL_ITEMS...]}
MATERIAL_ITEMS:
TEXTURE | INTERIOR
Example
#declare MyGlass=material{texture{Glass_T} interior{Glass_I}}
object{MyObject material{MyGlass}}
Fixed problem with media and no light sources.
Fixed memory leak in mesh
Fixed erronious missing pigment in fully textured mesh
Fixed repeat warp flip bug from 3.02
Fixed multi-dimension array initializer bug
Fixed multi-density in declared media bug
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> o Added new editor.
What is the name of the edit control you are using?
- mark
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Mark Arrasmith" <arr### [at] worldnet attnet> wrote:
>What is the name of the edit control you are using?
CodeMax. See www.winmain.com.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
>The changes to POVWIN itself are extensive and will be listed in this
>newsgroup to allow users to decide whether or not to download it.
it sounds great!! Especially the new material{} statement seems to be
fantastic :-D
I didn't download the new beta by now, but I hope the bug with
GUI-Extensions has been fixed too, because it hasn't been mentioned in
the changes summary... ??
Bye,
Friedemann
Friedemann Schmidt
Fri### [at] Stonescom
Raytracing-Gallery: http://www.rz.fhtw-berlin.de/~s0049669/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>I didn't download the new beta by now, but I hope the bug with
>GUI-Extensions has been fixed too, because it hasn't been mentioned in
>the changes summary... ??
yeah, it's fixed.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The beta 6 release has been delayed for a few days to fix a last-minute parser
bug.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team heeft geschreven in bericht
<35dfc6fb.18476197@news.povray.org>...
> o Added rubberband mode to render window for selection of render
region.
Great! I hope the re-rendered region is shown in the original rendering to
see the differences.
BTW:
I downloaded beta 5 only yesterday so there will be another 5.5 meg to pull,
I am afraid :-(.
Is there any schedule in the betas?
Frans.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>Great! I hope the re-rendered region is shown in the original rendering to
>see the differences.
Nope, it's not. That would have involved too many changes. If someone wants
that feature it would be almost trivial to implement as a GUI extension.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>CodeMax. See www.winmain.com.
They don't support AlphaNT though they did say . . .
<snip>
Alpha NT is not supported, but you could quite easily port the code, making
only minor big/little-endian and structure-alignment changes to the source.
</snip>
Hmm, $400 is alot to just try and port it to Alpha. Anyone besides me
really want to try? Or am I going to have alot of explaining to my wife?
:)
- mark
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team wrote in<35e12f16.110664006@news.povray.org>...
>If someone wants that feature it would be almost trivial to implement as a
GUI extension.
Sorry, I do not understand that part of your answer. English is not my first
language, but according to my dictionary 'trivial' means either 'not
important', 'commonplace', or 'lacking seriousness'. What I meant is that it
would be a useful feature when, for example, fine tuning light strength,
bump values, etc. Admittedly, one could load the original picture in say
photoshop, copy the rendered patch into it, and move the patch around till
it fits, and one could see the effect of the changes made, provided you have
no trouble with POV opening a file being used by photoshop, etc. In my
opinion, the feature would allow the user to speed up the tuning process,
and therefore in that respect it is both important and serious, and
certainly not commonplace.
The feature would nescessarily be provided by the GUI, which has shown the
picture the user is not satisfied with, which has allowed the user to make
the changes, and which has allowed the user to indicate the area on which he
wants a test for his new settings. In view of the above, it is not beyond
the scope of the GUI to allow the user a good comparison.
povray.org admin team also wrote in<35e12f16.110664006@news.povray.org>...
>That would have involved too many changes.
Ok, that's a VERY good reason for not implementing it. I do not know the POV
code, but I take it is complex. I just creep on with a bitmap editor and
renamed files.
Thank you for the work you do!
Frans
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
