If I pass an inc file as command line parameter (or, more usefully,
try to open an inc file in the Windows editor from Windows Explorer
by double-clicking), this attempts to process the file as an INI
file, then chokes on it (this is not a valid ini file).

Tested using 3.7 RC3 Windows x64 version. I would have expected
the file to be opened in the editor as with pov files.

Post a reply to this message

Christian Froeschlin <chr### [at] chrfrde> wrote:
> If I pass an inc file as command line parameter (or, more usefully,
> try to open an inc file in the Windows editor from Windows Explorer
> by double-clicking), this attempts to process the file as an INI
> file, then chokes on it (this is not a valid ini file).
>
> Tested using 3.7 RC3 Windows x64 version. I would have expected
> the file to be opened in the editor as with pov files.

To me this sounds like a problem initiated by a third-party app that uses it's
own way of handling files, using ".ini" as extension.
It seams, that some bug in it also has being affected the way of handling files
that comes with a ".inc" extension.

Try to (right click) open the .inc-file with the "open with"- context and don't
chose an application from the list. Instead chose one by browsing manually and
than point to the editor, or to wordpad.

This /may/ work.

Post a reply to this message

On 11.08.11 03:58, H. Karsten wrote:
> Christian Froeschlin<chr### [at] chrfrde>  wrote:
>> If I pass an inc file as command line parameter (or, more usefully,
>> try to open an inc file in the Windows editor from Windows Explorer
>> by double-clicking), this attempts to process the file as an INI
>> file, then chokes on it (this is not a valid ini file).
>>
>> Tested using 3.7 RC3 Windows x64 version. I would have expected
>> the file to be opened in the editor as with pov files.
>
> To me this sounds like a problem initiated by a third-party app that uses it's
> own way of handling files, using ".ini" as extension.
> It seams, that some bug in it also has being affected the way of handling files
> that comes with a ".inc" extension.

??? This is not what he says at all. He says that when opening an inc file 
that is correctly associated with POV-Ray is parsed as INI file rather than 
being opened in the editor.

So the question is how 3.6 behaved or if this is a new bug in the command 
line parser.

	Thorsten

Post a reply to this message

Thorsten Froehlich wrote:

> ??? This is not what he says at all. He says that when opening an inc 
> file that is correctly associated with POV-Ray is parsed as INI file 
> rather than being opened in the editor.

yes this is corrcet.

> So the question is how 3.6 behaved or if this is a new bug in the 
> command line parser.

I just tried with 3.6 and it also tries to parse as ini. Bowever,
it's less noticeable, as 3.6 only displays the error in the status
bar, while 3.7 opens an error box.

Post a reply to this message

Christian Froeschlin <chr### [at] chrfrde> wrote:
> Thorsten Froehlich wrote:
>
> > ??? This is not what he says at all. He says that when opening an inc
> > file that is correctly associated with POV-Ray is parsed as INI file
> > rather than being opened in the editor.
>
> yes this is corrcet.
>
> > So the question is how 3.6 behaved or if this is a new bug in the
> > command line parser.
>
> I just tried with 3.6 and it also tries to parse as ini. Bowever,
> it's less noticeable, as 3.6 only displays the error in the status
> bar, while 3.7 opens an error box.

Ok, that's indeed a completely different thing.

How's your settings in the explorer; do you see your file-extensions in the
explorer, or are they hidden?

Post a reply to this message

On 11.08.11 22:26, Christian Froeschlin wrote:
> Thorsten Froehlich wrote:
>
>> ??? This is not what he says at all. He says that when opening an inc file
>> that is correctly associated with POV-Ray is parsed as INI file rather
>> than being opened in the editor.
>
> yes this is corrcet.
>
>> So the question is how 3.6 behaved or if this is a new bug in the command
>> line parser.
>
> I just tried with 3.6 and it also tries to parse as ini.

Hmm, I would suggest to open a feature request in the bug tracker then. It 
might also be a bug, but without the code at hand right now I can't ell.

	Thorsten

Post a reply to this message

On 8/08/2011 01:09, Christian Froeschlin wrote:
> If I pass an inc file as command line parameter (or, more usefully,
> try to open an inc file in the Windows editor from Windows Explorer
> by double-clicking), this attempts to process the file as an INI
> file, then chokes on it (this is not a valid ini file).
> 
> Tested using 3.7 RC3 Windows x64 version. I would have expected
> the file to be opened in the editor as with pov files.

Any file not recognized as a POV file will be considered an INI file
by the command-line parser. This is standard POV-Ray behavior since
more or less the beginning of time (or at least since we stopped
living in caves :-)

Even if you have associated INC's with POVWIN via the windows
registry, POVWIN doesn't know that it's meant to be edited unless you
explicitly tell it to do so by passing the /EDIT command-line
parameter as well. If you look at the standard associations for the
.POV file type (as set up by the POV installer), you will see that is
exactly what it does. If you right-click on a POV file, you will see
that you are given two POV-specific options: 'Open with POV-Ray' and
'Edit with POV-Ray'.

So you need to tell windows explorer to pass the /EDIT switch before
the filename.

-- Chris

Post a reply to this message

Chris Cason wrote:

> So you need to tell windows explorer to pass the /EDIT switch before
> the filename.

ok, thanks. It might be worth setting this association up  for
inc files in the installer as well (rendering an inc file or opening
it as ini will usually not make sense).

Post a reply to this message