 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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 also switched out the word "Text"
for Mcro (1 instance of it) where the others are found at. The old Write
program (from Win 3.1) does this well if just doing a Edit/Search/Replace
after opening the cmedit.dll file and select No Conversion when prompted.
Unless you're familiar with it the newer Write.exe (20KB or 5KB) is just a
front for Wordpad.exe currently in Win9* and won't work far as I know. I've
tried the MS-DOS Edit.com for this sort of thing too and it doesn't do it
right either. If anyone knows of another non-formatting editor which can
successfully do this too the time is now to speak up.
So.... I managed to add in a *.mcr to the File/Open... and File/Save
as... lists this way. Then associated the mcr extension with POV-Ray to
Edit any of those files when clicking on them in Explorer. In case someone
doesn't know how: Run Explorer, go to View/(Folder) Options... and the File
Types tab there. Press the New Type button and put POV macro (or similar)
in the top field, mcr (or whatever extension you chose earlier) in the next,
then skip down to New button below Actions:. Now enter Edit for the action
and choose the pvengine.exe path with the Browse button, adding /EDIT "%1"
to the end after that.
The syntax hilighting still will not function automatically so to see it
you're going to have to right-click (or Alt-Enter) in the file while it's
open in the editor to get to the Properties and select POV-Ray for the
language.
Bob
--
// omniVERSE
// http://users.aol.com/inversez/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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.
--
Ken Tyler - 1200+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 2 Dec 1999 13:33:55 -0600, "omniVERSE" <inv### [at] aol com> wrote:
>If anyone knows of another non-formatting editor which can
>successfully do this too the time is now to speak up.
Bob, it's probably easier to use a hex editor for binary files. I use
Frhed by Raihan Kibria but there are some that are even easier to use.
http://homepages.hrz.tu-darmstadt.de/~rkibria/
Freeware, complete with source.
--
Alan - ako### [at] povrayorg - a k o n g <at> p o v r a y <dot> o r g
http://www.povray.org - Home of the Persistence of Vision Ray Tracer
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thanks for the lead Alan, although I really don't try to do anything more
than this type of simple surgery on a Windows program like Notepad and Write
to allow me to open differing file extensions easier, and POV-Ray for
Windows comes under that heading as well.
I really should have added a disclaimer about "hacking" the source code of
licensed programs by doing this kind of thing. Guessing most anyone doing
so know the routine about not reselling or distributing a modified program
to seem another custom one in case of potential consequence.
Bob
Alan Kong <ako### [at] povrayNO-SPAMorg> wrote in message
news:saod4scdsgf3ef4ku4sc8jqkim3s5h5dc0@4ax.com...
> On Thu, 2 Dec 1999 13:33:55 -0600, "omniVERSE" <inv### [at] aolcom> wrote:
>
> >If anyone knows of another non-formatting editor which can
> >successfully do this too the time is now to speak up.
>
> Bob, it's probably easier to use a hex editor for binary files. I use
> Frhed by Raihan Kibria but there are some that are even easier to use.
>
> http://homepages.hrz.tu-darmstadt.de/~rkibria/
>
> Freeware, complete with source.
>
> --
> Alan - ako### [at] povrayorg - a k o n g <at> p o v r a y <dot> o r g
> http://www.povray.org - Home of the Persistence of Vision Ray Tracer
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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] povrayorg> 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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 2 Dec 1999 22:29:43 -0600, omniVERSE wrote:
>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?
Well, one could do what emacs does and say that if a file starts with a
line that says (I think)
// -*- POV -*-
then it's a POV file. But I'm not sure I see the need to pass these
associations around. Someone getting a .ron file from me can feel free
to add their own association once they realize it's a POV file, or they
can just set the POV-language mode manually as they would now.
--
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
|
|
| |
| |
|
|
|
|
| |
