 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
If you have beta POV-Ray for Windows v3.1 beta 6 installed, this is all you
need to update to beta 6b.
ftp://ftp.povray.org/pub/povray/beta/beta3.1-6b/winupd.zip
Just unzip it into the <installdir>\bin directory.
If you downloaded a version of 6b that complains about a missing DLL, then this
update will also fix that.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team schrieb in Nachricht
<35ec0034.5949324@news.povray.org>...
>If you have beta POV-Ray for Windows v3.1 beta 6 installed, this is all you
>need to update to beta 6b.
Thats a real good idea with the update, i hope that you always
have one alternatively, because it is simpler to just copy the main
exe (plus two or three secondary files ), without changing all parameters
again.
it would be also simpler, to get back the old version when i have problems
with the new one
E-MAIL : spa### [at] snafu de ( remove spam. )
Homepage : http://www.snafu.de/~lars.wolter
ICQ-UIN : 4137784
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team wrote in message <35ec0034.5949324@news.povray.org>...
>If you have beta POV-Ray for Windows v3.1 beta 6 installed, this is all you
>need to update to beta 6b.
>
> ftp://ftp.povray.org/pub/povray/beta/beta3.1-6b/winupd.zip
>
>Just unzip it into the <installdir>\bin directory.
>
>If you downloaded a version of 6b that complains about a missing DLL, then
this
>update will also fix that.
#If updates (not new betas) are likely to appear frequently, #then it might
be a good idea to have a patch for download, one that only makes the
necessary changes to the necessary files... if they are small.
Just an idea.
Peter
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I have noticed a behavior of the new editor that is kind of troublesome.
Why specifically do you say 'new editor' here ? Insofar as I can recall this
behaviour is no different to that of the old editor. In neither case is the
editor responsoble for the behaviour of the message window.
So, is there something different about this that didn't happen in v3.02 ?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>dance. This was not the behavior of the editor I used in 3.01. It would
>smoothly send to screen in the message window the warning message but
>did not flicker and did not make the scroll bar dance.
well why not just turn off the small message window instead of complaining
about the way it behaves ? (you _did_ read the release notes, didn't you ... ?)
>( I did notice the new editor allows you to now purge the message base bravo!).
I'm not sure what you're referring to. You've been able to purge messages for
at least a year (it was in 3.02), so if it's not that then what do you mean ?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team wrote in message
<35ec0034.5949324@news.povray.org>...
>If you have beta POV-Ray for Windows v3.1 beta 6 installed, this is
all you
>need to update to beta 6b.
Got a new bug with the update.
clicking on the 'Codemax properties' 'keyboard' tab brings
this error:
Access violation at address 00A584EB in module 'CMAX101.dll'
read of address FFFFFFFF.
The tab does appears correctly, but I can do nothing of it,
because:
PVENGINE caused an invalid page fault in
module CMAX101.DLL at 0137:00a56ea6.
Registers:
EAX=00000000 CS=0137 EIP=00a56ea6 EFLGS=00010206
EBX=bff64db6 SS=013f ESP=0073f36c EBP=00000000
ECX=00000018 DS=013f ESI=0073f4b0 FS=35a7
EDX=00a56ea6 ES=013f EDI=5e5fe98e GS=0000
Bytes at CS:EIP:
8b 4d 70 8d 54 24 38 80 e5 7f 52 80 cd 40 6a 00
Stack dump:
0073f4b0 00008522 00000000 00000d38 00000000 00000000 83b40283
16ef36d3 00000000 00000000 00000467 04670000 00000000 00000000
0000851c 0073f4e0
I didn't have this bug with beta 6A
----------------------------------------------------------------
POV INFO
----------------------------------------------------------------
POV-Ray for Windows
Version 3.1.beta.6.watcom.win32 [Pentium II optimised]
----------------------------------------------------------------
SYSTEM INFO
----------------------------------------------------------------
MS Windows 95 4.00.950 B
IE 4.0 4.711712.6
Pentium Pro 233MHz
192MB RAM
----------------------------------------------------------------
thank you thank you thank you thank you thank you thank you
----------------------------------------------------------------
THANK YOU FOR MAKING POV-RAY
IT IS WONDERFULL
Sincerely,
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Three (very) minor annoyances:
*material isn't syntax highlighted
*nested comments /*/**/*/ aren't highlighted correctly
*ctrl+o doesn't work in the message window - as when you
launch an 'empty' pov
Povingly,
Philippe
----------------------------------------------------------------
POV INFO
----------------------------------------------------------------
POV-Ray for Windows
Version 3.1.beta.6.watcom.win32 [Pentium II optimised]
----------------------------------------------------------------
SYSTEM INFO
----------------------------------------------------------------
MS Windows 95 4.00.950 B
IE 4.0 4.711712.6
Pentium Pro 233MHz
64MB RAM
----------------------------------------------------------------
thank you thank you thank you thank you thank you thank you
----------------------------------------------------------------
THANK YOU FOR MAKING POV-RAY
IT IS WONDERFULL
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Philippe Debar <phi### [at] hotmailcom> wrote:
: *nested comments /*/**/*/ aren't highlighted correctly
(I have not ever seen winpov, but...)
Dou mean that in a code like:
/* test1 /* test2 */ test3 */
'test1' and 'test2' are highlighted as commented but 'test3' not?
That's the right way, since 'test3' is not commented and the last */ is
a syntax error (if I remember the documentation right and it works exactly
like in C).
Or do you mean that 'test3' _is_ highlighted and it shouldn't?
--
- Warp. -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nieminen Mika wrote in message <35ed6e46.0@news.povray.org>...
>Philippe Debar <phi### [at] hotmailcom> wrote:
>>: *nested comments /*/**/*/ aren't highlighted correctly
> (I have not ever seen winpov, but...)
> Dou mean that in a code like:
>/* test1 /* test2 */ test3 */
> 'test1' and 'test2' are highlighted as commented but 'test3' not?
Yes exactly
> That's the right way, since 'test3' is not commented and the last
*/ is
>a syntax error (if I remember the documentation right and it works
exactly
>like in C).
Well, pov does support nested comments. It parses and render
correctly.
From the doc:
/* ... */ comments can be nested, the following is legal:
/* This is a comment
// This too
/* This also */
*/
So it isn't exactly like: it is better!
Povingly,
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The new context menu is great!
Thank you programing peoples!
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
