I don't know how many people save macro includes with the *.mcr
extension, but I was thinking it would be great if the Open Dialogue
(Windows version) had an option for seeing *.mcr, along with *.pov,
*.inc, and *.ini. Just a thought.

Post a reply to this message

"Dave Dunn" <poi### [at] aolcom> schrieb im Newsbeitrag
news:3D6650B8.708CB49E@aol.com...
> I don't know how many people save macro includes with the *.mcr
> extension, but I was thinking it would be great if the Open Dialogue
> (Windows version) had an option for seeing *.mcr, along with *.pov,
> *.inc, and *.ini. Just a thought.

In what way is a *.mcr file different from an *.inc file other than the
different extension -- obviously in no way, so why not simply use *.inc in
the first place?

    Thorsten

Post a reply to this message

"Dave Dunn" <poi### [at] aolcom> wrote in message
news:3D6650B8.708CB49E@aol.com...
> I don't know how many people save macro includes with the *.mcr
> extension, but I was thinking it would be great if the Open Dialogue
> (Windows version) had an option for seeing *.mcr, along with *.pov,
> *.inc, and *.ini. Just a thought.
>
I stopped using the .mcr extension in favour of .inc simply because .mcr
files weren't supported by the codemax editor as POV files.

-tgq

Post a reply to this message

"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3d665425@news.povray.org...
>
> In what way is a *.mcr file different from an *.inc file other than the
> different extension -- obviously in no way, so why not simply use *.inc in
> the first place?
>

I suppose that he wants to distinguish between include files which contain
objects or texture/etc. definitions, and macro files containing, well, macros.

Not something I feel the need for, but as an idea, being able to add additional
extensions to the codemax editor might be a nice minor feature.

BTW If dave's desperate for it, and doesn't mind losing *.ini from the general
pov file types, then a cautious edit of cmedit.dll will allow you to see *.mcr
files

Post a reply to this message

Dave Dunn <poi### [at] aolcom> wrote in message
news:3D6650B8.708CB49E@aol.com...
> I don't know how many people save macro includes with the *.mcr
> extension, but I was thinking it would be great if the Open Dialogue
> (Windows version) had an option for seeing *.mcr, along with *.pov,
> *.inc, and *.ini. Just a thought.
>
>

I use *.inc for macro type include files and *.txt (which already has a
"slot") for data type include files.

 -Shay

Post a reply to this message

Thorsten Froehlich wrote:

> In what way is a *.mcr file different from an *.inc file other than the
> different extension -- obviously in no way, so why not simply use *.inc in
> the first place?

I didn't mean to cause a big debate here. The point is that I distingush
between includes for things like textures, meshes etc.(inc), and macros (mcr).
If I need to find one of my macro files in a hurry, it would be nice to see
them all listed by extension. Also, I would like to be able to have "mcr" be a
Save As option. There is no real programming reason, only an ease of use one.

Post a reply to this message

Dave Dunn wrote:
>I don't know how many people save macro includes with the *.mcr
>extension, but I was thinking it would be great if the Open Dialogue
>(Windows version) had an option for seeing *.mcr, along with *.pov,
>*.inc, and *.ini. Just a thought.
>
Just type in *.mcr and hit enter to see them.

=RAY=

Post a reply to this message

=RAY= wrote:

> Just type in *.mcr and hit enter to see them.

Well, gee, why didn't I think of that? In that case, we could just have
the All Files option with no specific file types in the Open and Save As
menus and search that way for *.pov, *.inc, and *.ini, and save a half a
line of precious code in cmedit.dll.

Post a reply to this message