Hello,

I hope this is of some help to know about. I have noticed that if I
cut and paste a POV-Ray scene into the editor, the color syntax
highlighting fails to operate on the newly created file.

Try this:

1) Open a valid POV file in the windows editor

2) "Select-All" and copy to the windows clip board

3) Click "File-New File" to create a new file

4) Paste the clipboard contents into the new file

5) Save the new file with a typical POV extension

6) Notice that the new file has no color highlighting

7) Close the file and reopen - still no highlights

8) Close POV and reload it - that file is still the same

9) Reboot computer and retry - the file is still the same


Both files will have seemingly identical information stored in them,
but only the first one is color highlighted. Why?

I first learned of this by inserting the "Ready-made scene" named
"Basic Scene" into an empty and newly created file in the editor.
Doing this caused no highlighting. I saved the file with an
appropriate name, and still no highlighting. It is still black and
white no matter what I try. Is this to be expected? Perhaps this is a
"feature" of CodeMax. If so, I need to find out how to work around it.

Thanks for your time,
Glen Berry

Home -> http://www.ezwv.com/~mclilith/index.html
IMP  -> http://www.algonet.se/~jhubert/MovieProject/index.html

To reply via personal email, remove the "X" from Xno### [at] ezwvcom

Post a reply to this message

G. Berry wrote in message <35f2dacc.42966358@news.povray.org>...
>Hello,
>
>I hope this is of some help to know about. I have noticed that if I
>cut and paste a POV-Ray scene into the editor, the color syntax
>highlighting fails to operate on the newly created file.
>


It works home (3.1 beta 6b)

>Try this:
>
>1) Open a valid POV file in the windows editor
>
>2) "Select-All" and copy to the windows clip board
>
>3) Click "File-New File" to create a new file
>
>4) Paste the clipboard contents into the new file
>
>5) Save the new file with a typical POV extension
>
>6) Notice that the new file has no color highlighting
>

Yes it has... tried it thrice. I don't know why it doesn't work on your PC.
Can you provide mode info ( OS, hardware...)?

<snip>

>Thanks for your time,
>Glen Berry
>
>Home -> http://www.ezwv.com/~mclilith/index.html
>IMP  -> http://www.algonet.se/~jhubert/MovieProject/index.html
>
>To reply via personal email, remove the "X" from Xno### [at] ezwvcom

Peter

Post a reply to this message

What you need to do, is go into the CodeMax properties, select the language
tab, and choose "Pov-Ray" from the drop down list. After that it'll work.

(I got bit by this one too)

--
--
Twyst -------------------------------------------
twysted mynd - for pov-ray news, reviews and tutorials
http://twysted.net
PatchStation - a central repository for Pov-Ray patches.
http://twysted.net/PatchStation
e-mail: twy### [at] twystednet
---------------------------------------------------

Post a reply to this message

On Mon, 7 Sep 1998 01:05:30 +0300, "Peter Popov" <pet### [at] usanet>
wrote:

>
>
>G. Berry wrote in message <35f2dacc.42966358@news.povray.org>...
>>Hello,
>>
>>I hope this is of some help to know about. I have noticed that if I
>>cut and paste a POV-Ray scene into the editor, the color syntax
>>highlighting fails to operate on the newly created file.
>>
>
>
>It works home (3.1 beta 6b)
>
>>Try this:
>>
>>1) Open a valid POV file in the windows editor
>>
>>2) "Select-All" and copy to the windows clip board
>>
>>3) Click "File-New File" to create a new file
>>
>>4) Paste the clipboard contents into the new file
>>
>>5) Save the new file with a typical POV extension
>>
>>6) Notice that the new file has no color highlighting
>>
>
>Yes it has... tried it thrice. I don't know why it doesn't work on your PC.
>Can you provide mode info ( OS, hardware...)?
>
><snip>
>

Here are my system specifications:

POV-Ray version:  3.1.beta.6b.watcom.win32[Pentium II optimized]
Operating System:  WIN95, OSR1
Computer:  Generic Pentium 133 system with 32MB of RAM

Thanks,
Glen Berry

Home -> http://www.ezwv.com/~mclilith/index.html
IMP  -> http://www.algonet.se/~jhubert/MovieProject/index.html

To reply via personal email, remove the "X" from Xno### [at] ezwvcom

Post a reply to this message

On Sun, 6 Sep 1998 16:53:58 -0700, "Twyst" <Twy### [at] twystednet> wrote:

>What you need to do, is go into the CodeMax properties, select the language
>tab, and choose "Pov-Ray" from the drop down list. After that it'll work.
>
>(I got bit by this one too)
>

Okay, can we PLEASE make the default language be POV-Ray?   :)

My editor keeps reverting to <none> each time I open a new file. Since
this is an editor built into POV-Ray, having POV-Ray be the default
language seems very appropriate. I wonder how many other settings
change themselves automatically when a new file is created?

Thanks Twyst. I know how to work around this little feature now.

Later,
Glen Berry

Home -> http://www.ezwv.com/~mclilith/index.html
IMP  -> http://www.algonet.se/~jhubert/MovieProject/index.html

To reply via personal email, remove the "X" from Xno### [at] ezwvcom

Post a reply to this message

Xno### [at] ezwvcom (G. Berry) wrote:

>this is an editor built into POV-Ray, having POV-Ray be the default
>language seems very appropriate. 

The default is chosen according to the extension. We will not make
POV a 'default' for all files because people will complain.

As for the fact that .POV isn't chosen when you do a save as, that's
fixed in the next version. 

> I wonder how many other settings change themselves automatically when
> a new file is created?

If you'd read the release notes and had a bit of a play with the editor
properties, you wouldn't have needed to post here (or send us two emails
**as well**) asking how to fix it.

In future if you want to rely on assistance from others to solve your
problems, at least do us the courtesy of choosing one or the other. If
I'd known that you also posted to the newsgroup I wouldn't have taken
the time to personally answer your email (not that it took very long,
but it was still a waste of my time, because it is now clear that you
already knew the answer before I even sent the reply).

Post a reply to this message

You need to do this when you open a new file too

took me ages to find that one out not being very bright!!!

Mick Hazelgrove

Twyst <Twy### [at] twystednet> wrote in article <35f3139c.0@news.povray.org>...
> What you need to do, is go into the CodeMax properties, select the
language
> tab, and choose "Pov-Ray" from the drop down list. After that it'll work.
> 
> (I got bit by this one too)
> 
> --
> --
> Twyst -------------------------------------------
> twysted mynd - for pov-ray news, reviews and tutorials
> http://twysted.net
> PatchStation - a central repository for Pov-Ray patches.
> http://twysted.net/PatchStation
> e-mail: twy### [at] twystednet
> ---------------------------------------------------
> 
> 
> 
>

Post a reply to this message

Twyst wrote in message <35f3139c.0@news.povray.org>...
>What you need to do, is go into the CodeMax properties, select the language
>tab, and choose "Pov-Ray" from the drop down list. After that it'll work.
>
>(I got bit by this one too)
>


Now I remember I did this the moment I saw this option, which was while I
was exploring the new editor features. Probably that's why I didn't have any
problems with syntax highlightning.

>--
>Twyst -------------------------------------------
>twysted mynd - for pov-ray news, reviews and tutorials
>http://twysted.net
>PatchStation - a central repository for Pov-Ray patches.
>http://twysted.net/PatchStation
>e-mail: twy### [at] twystednet
>---------------------------------------------------
>

Peter

Post a reply to this message

On Mon, 07 Sep 1998 01:09:07 GMT, new### [at] DESPAMpovrayorg
(povray.org admin team) wrote:

>Xno### [at] ezwvcom (G. Berry) wrote:
>
>>this is an editor built into POV-Ray, having POV-Ray be the default
>>language seems very appropriate. 
>
>The default is chosen according to the extension. 

That's not totally correct! The extension of the file can activate the
syntax highlighting feature, but *only* if the file is not currently
on the MRU list. In that case, the MRU's language settings will
override the language setting normally suggested by the file's
extension.  (This is not in ANY of the documentation.)

>We will not make
>POV a 'default' for all files because people will complain.
>
When I asked for POV-Ray's editor to make "POV-Ray" the default
language, I meant for *new* files saved with ".pov" and ".inc"
extensions, to be automatically recognized as POV-Ray files by the
editor, and to use "POV-Ray language" syntax highlighting on them by
default, instead of not highlighting them at all. 

>As for the fact that .POV isn't chosen when you do a save as, that's
>fixed in the next version. 
>

This sounds like you plan on fixing the very bug I was originally
trying to notify you about, but got my head bit off in this newsgroup,
when I dared to casually discuss it here, after sending in a proper
bug report. You spend one sentence in your post to tell me the most
important thing: that the situation is getting "fixed". That's all you
needed to say. Then you waste most of your post below on sarcasticly
antagonizing me after I tried to be helpful and submit a bug report.

>> I wonder how many other settings change themselves automatically when
>> a new file is created?
>
>If you'd read the release notes

I read plenty of things!!! 

1) All applicable things on the POV-Ray website
2)  The "README" file at the ftp.povray.org site
3) The "Read.me" file in my POV-Ray installation directory.
4) The "Readme.doc" file in the same directory.
5) The "povwin.doc" file.
6) The "Povwhere.get" file - not related to this, but I did read it.
7) The "Povlegal.doc" file - not related to this, but I did read it.
8) The "Betanews.txt" file.
9) The "changes.txt" file.
10) Three Windows format help files.

I despise your automatically assuming I didn't read the documents
before posting or sending email.

> and had a bit of a play with the editor properties, 

Does a couple hours of frustration with trying to get consistent
editor syntax highlighting sound like enough "play" to you? Don't dare
belittle me like that, as if I didn't make an effort.

>you wouldn't have needed to post here

I did the very things you have mentioned and guess what? I still
needed to post here!

> (or send us two emails >**as well**)  asking how to fix it.

I had found frustrating, undocumented behaviour. It  sure seemed like
a bug to me. Not because it was a "feature" that I just didn't like,
but because the program was behaving in a way that was contradictory
to what documentation existed so far. The documentation clearly states
that the new editor would recognize files with ".pov" extensions as
being POV syntax. I was saving files in the ".pov" extension, and the
editor wasn't recognizing them as such. 

Having to explicitly tell the editor that each new file is in the POV
language, is *not* the same thing as the editor *recognizing* the file
as being in the language.

Yes, of course, I "had a bit of play" with the CodeMax properties. One
of the first things I did when I installed the program was to set each
and every option available to suit my personal taste. When I started
having trouble with the syntax highlighting, I checked the "language"
setting several times. Each time I checked it, it always said
"POV-Ray". 

No one told me that the instant that I clicked "File New", that the
previously affirmed "POV-Ray" setting would automatically change to
"<none>". Since the other settings were staying the same after I set
them, I expected that the language setting would stay the same also.
Even if the language *did* temporarily revert to "<none>", according
to *your* docs, I was lead to believe the moment I save the file as a
".pov" file, it should be recognized as having POV-Ray syntax. 

Since this is a beta test, it is entirely appropriate to send email to
the Bug Report address to alert you of a possible bug. I sent all the
actually pertinent information to you in the first email. Then I
realized that I had omitted some information that your help file
practically demands to be included with each bug report. I had forgot
to send you my computer and OS stats. I am sorry about that. So to
fufill the help file's request, I sent the second email moments after
the first, with the additional information.

Also in your help file message about bug reporting, you mention that I
shouldn't expect a personal answer from anyone on the POV-Team. After
reading that, I didn't expect you to answer my email.  I posted my
comments to the newsgroup in case *someone* in the newsgroup might
have some insight into the issue. Since the Bug Report address was not
to be considered a "user help desk" it seemed my only potential outlet
for feedback.

As for my, "asking how to fix it", as you phrased it above,  I never
asked you in my email "how do I fix this?".  Any sentences in that
email with question marks, contain merely *rhetorical* questions,
since I had already been told not to expect an answer from my email.

>In future if you want to rely on assistance from others to solve your
>problems, 

I wasn't asking anyone to solve one of *my* problems! I was alerting
the Bug Report address of what I considered to be a bug in POV-Ray,
which would be *your* problem, not mine. If you reread that little
note, it was very polite. It started out with the sentence: 

   "I hope this is of some help to know about..."

This is not the note of a person demanding help with their personal
problems. This was written by a person that tried merely to give you
the bug report feedback you had requested, and in the manner you had
requested it, to the best of his abilities. I don't appreciate your
smearing my character with your remark above.

>at least do us the courtesy of choosing one or the other.  If
>I'd known that you also posted to the newsgroup I wouldn't have taken
>the time to personally answer your email (not that it took very long,
>but it was still a waste of my time, because it is now clear that you
>already knew the answer before I even sent the reply).

Why are you exerting further effort and wasting even more of your time
by chastizing me in public like this, when I didn't even expect you to
write me in the first place? READ YOUR OWN MANUAL! I'm not to expect
an answer from a Bug Report! Just because *YOU* decided to write, and
failed to be first with a helpful answer is *NOT* a problem of mine! I
will not be criticized for *your* actions!

In the past, I have spoken positively on your behalf. I have said good
things about you and the rest of the POV-Team. I imagine you might
feel under some pressure in regards to developing POV. I have never
tried to pressure you or any POV-Team member into doing anything. In
fact, when people were clamoring for the release of POV 3.0, and some
people were making scornful remarks to the POV-Team on
"comp.graphics.rendering.raytracing", I came to your defense. I can
remember that you took the trouble to write an email to me then,
thanking me for the kind remarks I made on your behalf.

I have just one question:  (and you don't have to waste any of your
precious time actually responding here or via email - this is another
one of those rhetorical questions)


YOU USED TO BE A NICE FELLOW, WHAT HAPPENED TO YOU?

Post a reply to this message

>>The default is chosen according to the extension. 
>
>That's not totally correct! The extension of the file can activate the
>syntax highlighting feature, but *only* if the file is not currently

It is totally correct. The *default* is chosen according to the
extension, like I said. This is at the time the file is first
opened. It would also work at the time the file is first saved,
but that was not implemented in the version you had. After the
default is chosen automatically, you are free to manually change
it to anything you like, on a file by file basis.

>on the MRU list. In that case, the MRU's language settings will

The MRU retention of the language setting (amongst other things) is
entirely deliberate ; it's a feature that we explicitly coded into
the editor, not something that just 'happens'.

>override the language setting normally suggested by the file's
>extension.  (This is not in ANY of the documentation.)

Because the documentation is not written - something clearly and
specifically stated in the release notes. We also state that this
is BETA software and will have bugs, like the one you described.

We further say not to use the software if you are not prepared to
put up with some bugs. Reporting them is fine ; complaining about
them is not.

>This sounds like you plan on fixing the very bug I was originally
>trying to notify you about, but got my head bit off in this newsgroup,

We have made no secret of the fact that the 'save as' problem will be
fixed - something that we stated in the very same message as the one you
refer to above (re: bitten heads).

>Does a couple hours of frustration with trying to get consistent
>editor syntax highlighting sound like enough "play" to you? Don't dare
>belittle me like that, as if I didn't make an effort.

Come on ! I find it unbelievable that you claim to spend several HOURS
trying to use the simple, obvious, straightforward language setting
in the properties dialog ???

If that is the case, sir, then I say to you - don't use beta software!

>I had found frustrating, undocumented behaviour. It  sure seemed like

I will quote you from the changes file ...

  This release has a new editor in it. It may not work as expected. Remember
  that this is BETA software - don't use it if you're not prepared to put up
  with some bugs.

This same document states that the docs are not written. So I say to you again:
if this bothers you so much, don't use it ! It really annoys us that here you
are complaining about undocumented behaviour, when you have effectively been
warned to expect just this - no documentation and to expect bugs.

>No one told me that the instant that I clicked "File New", that the
>previously affirmed "POV-Ray" setting would automatically change to

The language setting is specific to each file - a common concept to
anyone familiar with code editors. This is knowledge that I would
expect of anyone willing to take on beta testing a new editor. The
setting you made of 'POV-Ray' _is_ retained - on the file that you
set it on. But the new file (which has, when it is created, no file
extension, and this no language type) has a type of 'none', just as
it should.

>"<none>". Since the other settings were staying the same after I set
>them, I expected that the language setting would stay the same also.

I quote you from the changes.txt:

  o Some properties only affect the current file, and some affect all files.
    Additionally, most (but not all) of those that affect the current file will
    become the default for any new files opened after that point. This is by
    design. For example, changing the tab stop setting only affects the current
    file, but will then become the default for new files from that point on.

It is clear from the above ('but not all') that you should not 'expect' the
language setting to stay the same. It may or may not. As it turns out, it's
not, and this is for an entirely logical and reasonable cause. How could the
language setting POSSIBLY be global, when it is possible to load files of
multiple types.

It did not occur to us that anyone could fail to understand this simple
concept.
    
>Since this is a beta test, it is entirely appropriate to send email to
>the Bug Report address to alert you of a possible bug. I sent all the

I have no objection to bug reports, as I state. I DO have an objection to
your tone.

>Also in your help file message about bug reporting, you mention that I
>shouldn't expect a personal answer from anyone on the POV-Team. After
>reading that, I didn't expect you to answer my email.  I posted my

I quote part of your message -

  Both files will have seemingly identical information stored 
  in them, but only the first one is color highlighted. Why?

  I first learned of this by inserting the "Ready-made scene"
  named "Basic Scene" into an empty and newly created file in
  the editor. Doing this caused no highlighting. I saved the
  file with an appropriate name, and still no highlighting. It
  is still black and white no matter what I try. Is this to be
  expected?

You pose two questions here. That sure looks like something that
you want an answer to ... from my point of view, it seemed that an
answer was appropriate. If your questions are rhetorical, fine, but
make sure we know that. There are sufficient numbers of people who
DON'T read (or care about) the bug reporting instructions that we
can't magically determine which is which.

I do not want any further discussion on this thread. There's no
point in continuing it as it'll only annoy both of us more. Please
do not follow up or reply via email.

Post a reply to this message