> I don't know what error you see? The first torus is orange and on the ground,
> the second is grey and vertical (since a rotation on x-axis is apply). All seems
> correct.

I can reproduce this strange behaviour reported by B. Gimeno completely. I have
used an other object from the insert menu (half hollowed rounded cylinder2)
instead of torus2. It was rendered correctly. I assume this is an issue with the
Windows Editor. May be that it doesn't recognise changes in some cases. I ever
use the option to save changes and render them by hitting the render button and
never experienced such an odd behaviour before.

Best regards,
Michael

Post a reply to this message

"MichaelJF" <mi-### [at] t-onlinede> wrote:
> > I don't know what error you see? The first torus is orange and on the ground,
> > the second is grey and vertical (since a rotation on x-axis is apply). All seems
> > correct.
>
> I can reproduce this strange behaviour reported by B. Gimeno completely. I have
> used an other object from the insert menu (half hollowed rounded cylinder2)
> instead of torus2. It was rendered correctly. I assume this is an issue with the
> Windows Editor. May be that it doesn't recognise changes in some cases. I ever
> use the option to save changes and render them by hitting the render button and
> never experienced such an odd behaviour before.
>
> Best regards,
> Michael

Or maybe the flag +C is set...

Post a reply to this message

"B. Gimeno" <nomail@nomail> wrote:
> I do not know if this is the right forum, since I've only checked in the windows
> version, please follow these instructions and confirm if you repeat the same
> strange error.
>
> 1.- Open a new file.
> 2.- Insert Menu -> Ready_Made Scenes -> Basic scene M2
> 3.- At the end of this scene Insert Menu -> Basic shapes -> torus 1
> 4.- Alt-G (you should have now an image of a yellow doughnut, yes?)
> 5.- Press Ctrol-Z ONCE (the torus code is deleted)
> 6.- Now Insert Menu -> Basic shapes -> torus 2
> 7.- Alt-G
> 8.- Here you have, the same result with another code.
>
> Try now, press Ctrol-Z (delete torus), Alt-G (generate the scene without torus),
> and insert the torus 2 again.
>
> In my test now is a vertical grey torus.
>
> English is not my native language and I'm using the google translator to write
> this post, my apologies to who might feel offended by my grammatical errors.
>
> Regards.
> B. Gimeno

 Sorry, I forgot to include the following information:
Pov-ray v.3.7
windows 7 64 bits

Post a reply to this message

>  Sorry, I forgot to include the following information:
> Pov-ray v.3.7
> windows 7 64 bits

I reproduced your findings with Windows 8.1 64 bit and POV 3.7.0 of course. And
no, +C still does not work correctly, so I didn't use it.

Best regards,
Michael

Post a reply to this message

"MichaelJF" <mi-### [at] t-onlinede> wrote:
> >  Sorry, I forgot to include the following information:
> > Pov-ray v.3.7
> > windows 7 64 bits
>
> I reproduced your findings with Windows 8.1 64 bit and POV 3.7.0 of course. And
> no, +C still does not work correctly, so I didn't use it.
>
> Best regards,
> Michael

I can't reproduce this error, I run on W732bits, maybe the 64 bits version is
bugged here.

Post a reply to this message

B. Gimeno wrote:
> ...
> 5.- Press Ctrol-Z ONCE...

Are you using autosave?  I haven't tried this on the current POV 
version, but I've noticed that in older versions, the "clean code/dirty 
code" detector DOES NOT DISTINGUISH between changes with the same number 
of keystrokes with a Ctrl-Z between them.  That is, if you type a line, 
save, use Ctrl-Z to undo the last character, and then type a different 
character, the editor doesn't recognize that the code has changed.

I know I'm not explaining this very well, since my fingers and my brain 
are all very cold right now ;) but if you watch the save button 
(grayed-out when the code is "clean") you can see this happen.

--Sherry Shaw

Post a reply to this message

> I don't know what error you see? The first torus is orange and on the ground,
> the second is grey and vertical (since a rotation on x-axis is apply). All seems
> correct.

Have you followed the instructions exactly?
If you have generated three images, the first should be a yellow torus torus and
the following two a gray torus. If you get two gray torus following my steps
WITHOUT TOUCHING ANY OTHER KEY, let us know, please. I have found that the
result is correct if touched (for example) the spacebar.

Regards,
B. Gimeno

Post a reply to this message

"Sherry K. Shaw" <ten### [at] aolcom> wrote:
> B. Gimeno wrote:
> > ...
> > 5.- Press Ctrol-Z ONCE...
>
> Are you using autosave?  I haven't tried this on the current POV
> version, but I've noticed that in older versions, the "clean code/dirty
> code" detector DOES NOT DISTINGUISH between changes with the same number
> of keystrokes with a Ctrl-Z between them.  That is, if you type a line,
> save, use Ctrl-Z to undo the last character, and then type a different
> character, the editor doesn't recognize that the code has changed.
>
> I know I'm not explaining this very well, since my fingers and my brain
> are all very cold right now ;) but if you watch the save button
> (grayed-out when the code is "clean") you can see this happen.
>
> --Sherry Shaw

I'm not quite sure I understand, but I've checked the source code of the two
objects do not have the same length and that the error does not occur if any
other key is pressed. Furthermore, when the second object is inserted the Save
button is not active, as someone mentioned before.

I have not been able to repeat this error with version 3.6 using the same 64-bit
computer with Windows 7.

B. Gimeno

Post a reply to this message

"B. Gimeno" <nomail@nomail> wrote:
> > I don't know what error you see? The first torus is orange and on the ground,
> > the second is grey and vertical (since a rotation on x-axis is apply). All seems
> > correct.
>
> Have you followed the instructions exactly?
> If you have generated three images, the first should be a yellow torus torus and
> the following two a gray torus. If you get two gray torus following my steps
> WITHOUT TOUCHING ANY OTHER KEY, let us know, please. I have found that the
> result is correct if touched (for example) the spacebar.
>
> Regards,
> B. Gimeno

You are right, the bug is alive and well! Maybe I have use some aother keys...

Lionel.

Post a reply to this message

B. Gimeno wrote:

>
> I'm not quite sure I understand, but I've checked the source code of the two
> objects do not have the same length and that the error does not occur if any
> other key is pressed.

The issue that I have seen is not with the length of the inserted code 
but rather with the actual number of physical keystrokes before and 
after the Undo operation.

Furthermore, when the second object is inserted the Save
> button is not active, as someone mentioned before.
>

If the Save button is not active, then this indicates that the editor 
does not recognize that the code has been changed since the last save. 
This becomes a problem with the autosave feature only because (1) the 
editor saves before running only if it recognizes that the code has 
changed since the last save and run; and (2) with autosaving enabled, 
there is no obvious warning that the changed code has not been saved. 
Thus, it is easily possible for the renderer dutifully to render the 
saved file, while properly ignoring the unsaved code in the editor, and 
to produce great confusion in the human at the keyboard--please note 
that I'm speaking from experience here.  ;)  I don't know if this is 
what's happening here, but the Ctrl-Z in the middle makes me suspect 
that this is the case.

--Sherry Shaw

Post a reply to this message