|
 |
This would be great, were it not for one thing. The user customizable
extensions (languages too?) would no doubt only work correctly on ones own
personal system and not on others so there would be a need for something
akin to distributable Ini files, such as now are possible, should anyone
want to share or distribute a certain file type. Some sort of
auto-recognition inherent to any and all POV-Ray files then? Hmm, that
might mean a binary instead of a ascii. What do you think?
Bob
Ron Parker <ron### [at] povray org> wrote in message
news:3846dc96@news.povray.org...
> On Thu, 02 Dec 1999 12:46:58 -0800, Ken wrote:
> >
> >
> >omniVERSE wrote:
> >>
> >> First thing to do is backup a copy of cmedit.dll.
> >> The changes I made to cmedit.dll are simply to replace txt with
mcr
> >> and there are 4 instances of that located in a obvious section of the
file
> >> (2 more exist but need not be changed).
> >
> > I really hate the idea of mucking around inside runtime libraries like
> >you are advocating, Bob. As a new founding member of TAG I will address
> >this issue with the POV-Team and get their feedback on it. Chris Cason
> >has mentioned some *possible* changes to the editor before release of
> >POV-Ray v3.5 and I might be able to get him to add this to it. This will
> >also allow for syntax highlighting of associated files within the editor
> >so it is a much better fix all the way around.
>
> I would suggest that the list of extensions that trigger automatic
> highlighting be configurable by the user, either through a dialog or
> through a registry entry of some kind. But that's just me.
>
> Currently, even the kind of hack Bob's proposing won't work around the
> fact that only POV and INC files get highlighted as POV files (source for
> cmedit.dll is in the official source distribution, but none of the patch
> authors seem to have ever looked at it.)
>
> --
> These are my opinions. I do NOT speak for the POV-Team.
> The superpatch: http://www2.fwi.com/~parkerr/superpatch/
> My other stuff: http://www2.fwi.com/~parkerr/traces.html
Post a reply to this message
|
|
