Bob, great that you tried to use it!

There is a problem if your normalized path names are very long (longer than
64 characters). The program doesn't deal with this: you could try to put the
images in a simpler path.

I'll upload the newer version (0.1.1.385). In it I have provided space for
longer path names, 256 chars.

Tell me if it works.
--
Regards,
Sander


omniVERSE <inv### [at] aolcom> schreef in berichtnieuws
3876baec@news.povray.org...
> And add your name to it somehow!  Sorry, not yelling, I just meant you
> should at least have some tie to yourself for such a thing.  Although come
> to think of it a email address wouldn't have hurt either, unless of course
> you wanted anonymity in the first place.
> I really like the utility, but it's teasing me so far with it
malfunctioning
> or because of whatever I'm not doing right.
>
> Bob

Post a reply to this message

Hello Ken,
If, after some more testing, the utility appears to be useful, I will. It
will then probably be a new site called something like "stols.net/pov".
There I could put also some of my POV output. I will let you know.
When Bob can't get it to work, I'll have to reconsider: what did I forget??
Ah:  old age....
--
Regards,
Sander


Ken <tyl### [at] pacbellnet> schreef in berichtnieuws
38769FB9.C4763239@pacbell.net...
>
> Sander,
>
> Will you be creating a permanent home for this. If you do I can provide
> a link to it on the povray.org links pages so that other people that
> might find it useful may be able to find it there.

Post a reply to this message

Sander <san### [at] stolscom> wrote:
: I'll upload the newer version (0.1.1.385). In it I have provided space for
: longer path names, 256 chars.

  Why there should be any limit?

-- 
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

Isn't there always?
What do _you_ suggest? Dynamic allocation of space? Or whatever it's called?
 I am just a layman, don't forget!
--
Regards,
Sander


Nieminen Juha <war### [at] punarastascstutfi> schreef in berichtnieuws
387893fe@news.povray.org...
> Sander <san### [at] stolscom> wrote:
> : I'll upload the newer version (0.1.1.385). In it I have provided space
for
> : longer path names, 256 chars.
>
>   Why there should be any limit?
>
> --
> 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

Sander <san### [at] stolscom> wrote:
: Isn't there always?
: What do _you_ suggest? Dynamic allocation of space? Or whatever it's called?
:  I am just a layman, don't forget!

  I don't know what language you are using, but if it's C++ then using a
string class will remove all static limits. You can read _any_ sized strings
into them.

-- 
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

Nieminen Juha wrote:
> 
> Sander <san### [at] stolscom> wrote:
> : Isn't there always?
> : What do _you_ suggest? Dynamic allocation of space? Or whatever it's called?
> :  I am just a layman, don't forget!
> 
>   I don't know what language you are using, but if it's C++ then using a
> string class will remove all static limits. You can read _any_ sized strings
> into them.

Even while passing a string from a Windows GUI app to a dos
command line utility ? I would think that the limiting factor
here would be the dos app.

-- 
Ken Tyler -  1300+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/

Post a reply to this message

Thanks, I'll try and see if I understand that.
The problem I'm having is -not- the size of the paths it seems now, but to
get the function
===========
DWORD GetShortPathName(
    LPCTSTR lpszLongPath, // points to a null-terminated path string
    LPTSTR lpszShortPath, // points to a buffer to receive the
null-terminated short form of the path
    DWORD cchBuffer  // specifies the size of the buffer pointed to by
lpszShortPath
   );
============
to operate properly in W95/98 as well as in WNT4.
--
Regards,
Sander


Nieminen Juha <war### [at] punarastascstutfi> schreef in berichtnieuws
3878aaab@news.povray.org...
>   I don't know what language you are using, but if it's C++ then using a
> string class will remove all static limits. You can read _any_ sized
strings
> into them.

Post a reply to this message

Sander wrote:
> 
> Isn't there always?
> What do _you_ suggest? Dynamic allocation of space? Or whatever it's
> called?
>  I am just a layman, don't forget!
> --
> Regards,
> Sander
> 

It seems like an 'academic' thing to me.
If the program works, with 256 char strings I think it'd be just fine in
most cases. Going beyond that might be interesting but is it really
relevant. How about POV-Rays output of animation frames? It's still
limited to 8 characters for the file names. It seems to me that that is
more a topic to worry about.
Besides that the maximum length of strings or paths is also depending on
platform as far as I know.

Remco

Post a reply to this message

That's what I originally thought. CMPEG only accepts 8.3 filenames, and I
have been busy a helluva time to get my "front end" to do just that. Works
fine with WNT4 but not with W9*, it appears..
Looking into it now...
--
Regards,
Sander


Ken <tyl### [at] pacbellnet> schreef in berichtnieuws
3878AA28.1EB08D96@pacbell.net...
> Even while passing a string from a Windows GUI app to a dos
> command line utility ? I would think that the limiting factor
> here would be the dos app.

Post a reply to this message

Remco de Korte wrote:
> 
> Besides that the maximum length of strings or paths is also depending
> on
> platform as far as I know.

Which of course is irrelevant here since we're talking about a Windows
shell 8)

Remco

Post a reply to this message