Since the introduction of macros with POV-Ray v3.1 many utility
macros have been introduced with a file extension of .MCR identifying
it as a Pov macro file. Naturally this is an underground movement but
since this is the way that Chris Colefax identifies them it is becoming
a standard designation for macro files.
  One unfortunate spin off from this is that POV-Win does not recognize
the .MCR file extension and any files opened or saved with that extension
are ignored by the editor and syntax highlighting is turned off by default.
It can of course be corrected by manually changing the language settings
for each file that you open or save with that extension but I suggest it
would be useful to add that extension as one recognized by the editor in
some future version of the program.

Cheers,

-- 
Ken Tyler
1100+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html

Post a reply to this message

Ken <tyl### [at] pacbellnet> wrote:
>   Since the introduction of macros with POV-Ray v3.1 many utility
> macros have been introduced with a file extension of .MCR identifying
> it as a Pov macro file. Naturally this is an underground movement but
> since this is the way that Chris Colefax identifies them it is becoming
> a standard designation for macro files.
>   One unfortunate spin off from this is that POV-Win does not recognize
> the .MCR file extension and any files opened or saved with that extension
> are ignored by the editor and syntax highlighting is turned off by
default.
> It can of course be corrected by manually changing the language settings
> for each file that you open or save with that extension but I suggest it
> would be useful to add that extension as one recognized by the editor in
> some future version of the program.

Oh dear - don't tell me I've gone and started another inconvenient trend?!
I guess being stuck in the age of DOS prompts and batch files blinds me to
the wider effects of picking and choosing file extensions as I please.
Actually, the main reason I originally chose to name the Automatic Clock
Modifier macro file with an extension other than INC was to make it clear
the file should be included once at the beginning of the main scene file, as
opposed to the behaviour of my previous files.

Using the INC extension would be more proper, of course: perhaps it's time
to think of returning to the correct file extension...

Post a reply to this message

Chris Colefax <cco### [at] geocitiescom> wrote:
: Using the INC extension would be more proper, of course: perhaps it's time
: to think of returning to the correct file extension...

  I think it's ok to make the difference between a file which declares
macros from files which don't.

  I have .mcr hooked in my emacs... :)

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Chris Colefax wrote:

> Oh dear - don't tell me I've gone and started another inconvenient trend?!

  I never said it was inconvenient. In fact I like the fact that it
differentiates a common include file from a macro bearing include
file. Helps to sort out the old technology from the new a progress
that should be embraced and not avoided.

> I guess being stuck in the age of DOS prompts and batch files blinds me to
> the wider effects of picking and choosing file extensions as I please.
> Actually, the main reason I originally chose to name the Automatic Clock
> Modifier macro file with an extension other than INC was to make it clear
> the file should be included once at the beginning of the main scene file, as
> opposed to the behaviour of my previous files.

  So there is more than just a preferential reason for having added a new
extention than just being a POV-Ray rebel. It helps define the usage of a
macro in a way that is not possible with pre-existing include files.
 
> Using the INC extension would be more proper, of course: perhaps it's time
> to think of returning to the correct file extension...

Proper ? I think it was a logical progression.

-- 
Ken Tyler
1100+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html

Post a reply to this message

Ken <tyl### [at] pacbellnet> wrote:
>   I never said it was inconvenient. In fact I like the fact that it
> differentiates a common include file from a macro bearing include
> file. Helps to sort out the old technology from the new a progress
> that should be embraced and not avoided.

followed by :
>   So there is more than just a preferential reason for having added a new
> extention than just being a POV-Ray rebel. It helps define the usage of a
> macro in a way that is not possible with pre-existing include files.

and finished with:
> Proper ? I think it was a logical progression.

I really don't know how much logic was involved...at any rate, here's one
possible solution: if you rename the *.MCR files to have both a MCR
extension *and* an INC extension (eg. AUTOCLCK.MCR becomes AUTOCLCK.MCR.INC)
then you should be able to include the files as before (using #include
"AUTOCLCK.MCR" without the INC extension), and still have the files properly
recognised as POV-Ray include files: the best of both worlds, perhaps?

Post a reply to this message

Chris Colefax wrote:

> I really don't know how much logic was involved...at any rate, here's one
> possible solution: if you rename the *.MCR files to have both a MCR
> extension *and* an INC extension (eg. AUTOCLCK.MCR becomes AUTOCLCK.MCR.INC)
> then you should be able to include the files as before (using #include
> "AUTOCLCK.MCR" without the INC extension), and still have the files properly
> recognised as POV-Ray include files: the best of both worlds, perhaps?

  I have close to 60 different macro files with a .mcr extention that
would require changing if I followed your suggestion. Additionaly other
platforms that I may wish to share files with would most likely choke
on this suggested format.

  Not being a windows programmer I have no clue as to how difficult
it would be to add support for a new extention. I say if it is fairly
easy to add support for then do so. If it's a major hassle then kiss
the idea off and I will crawl back under my rock and leave it alone.

Nothing ventured nothing gained.

-- 
Ken Tyler
1100+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html

Post a reply to this message

Ken once again replies ahead of a message post time (5 minutes).
  I was liking Chris' idea about the renaming, very plausible for Win9*.
You can usually switch around extensions in Windows programs fairly easy
without any programming at all, just careful editing of the source.  This
means dropping an already existing one, (Ini perhaps?).  Don't think that's
too feasible.  Oops, forgot that Ini doesn't get seen as POV-Ray script
anyway, that would mean dropping Inc, not going to happen.

Bob

Ken <tyl### [at] pacbellnet> wrote in message
news:37F6027E.F5AA9BC0@pacbell.net...
>
>
> Chris Colefax wrote:
>
> > I really don't know how much logic was involved...at any rate, here's
one
> > possible solution: if you rename the *.MCR files to have both a MCR
> > extension *and* an INC extension (eg. AUTOCLCK.MCR becomes
AUTOCLCK.MCR.INC)
> > then you should be able to include the files as before (using #include
> > "AUTOCLCK.MCR" without the INC extension), and still have the files
properly
> > recognised as POV-Ray include files: the best of both worlds, perhaps?
>
>   I have close to 60 different macro files with a .mcr extention that
> would require changing if I followed your suggestion. Additionaly other
> platforms that I may wish to share files with would most likely choke
> on this suggested format.
>
>   Not being a windows programmer I have no clue as to how difficult
> it would be to add support for a new extention. I say if it is fairly
> easy to add support for then do so. If it's a major hassle then kiss
> the idea off and I will crawl back under my rock and leave it alone.
>
> Nothing ventured nothing gained.
>
> --
> Ken Tyler
> 1100+ Povray, Graphics, 3D Rendering, and Raytracing Links:
> http://home.pacbell.net/tylereng/index.html

Post a reply to this message

If you are using Windows 9x can't you just right click on the file and
choose Open with... and then associate it with POV-Ray?

Post a reply to this message

TonyB wrote:
> 
> If you are using Windows 9x can't you just right click on the file and
> choose Open with... and then associate it with POV-Ray?

  Yes you can. What I am recommending however is not file associations
with windows so much as file associations with the internal editor.
Syntax highlighting is only supported for .pov and .inc files. I am
suggesting that the .dll file that establishes these associations be
changed to allow for the .mcr extention as well. I really don't think
it will be all that big of a job to do but this comes from a layman
and I have yet to hear a real programmers opinion on this subject.
 As I previously pointed out you can get syntax highlighting to work
with any extention if you go into the editor preferences and change
the language to POV-Ray. The downside to this is that if you close
the file and open it again you will have to reset it each time rather
than it being applied automaticaly based upon it's extention.

-- 
Ken Tyler
1100+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html

Post a reply to this message

Chris Colefax <cco### [at] geocitiescom> wrote:
: I really don't know how much logic was involved...at any rate, here's one
: possible solution: if you rename the *.MCR files to have both a MCR
: extension *and* an INC extension (eg. AUTOCLCK.MCR becomes AUTOCLCK.MCR.INC)

  The only problem here is that in pure DOS you will see the file is
AUTOCL~1.INC

  This may cause problems if you use povray for dos. #include "autoclck.mcr"
will certrainly not work.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message