 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich's furious key-hammering produced this:
>> (hint: use MacMegaPOV...the
>> official 3.5 doesn't use all the CPU power in OS X)
>
> This isn't true. This is only a rumor created by Chris Huff.
Right...that's why it's reproducable on my system (and yes, MacMegaPOV works
fine). I haven't tried the 3.5.1 preview yet, so I can't say anything about
that.
Followups set to povray.macintosh.
--
/*^*/light_source{100*<-5,2,-5>2}#macro I(i,n)#while(strlen(i)>=n)#local A=asc(
substr(i,n,1));#local a=asc(substr(i,n+1,1));cylinder{<div(A,8)-12,mod(A,8)-4,4
><div(a,8)-12,mod(a,8)-4,4>,0.1pigment{rgb z}}#local n=n+2;#end#end I("ScUe[]"1
/*<*/)I("mkmtlttk"1)//@_$#!,:<"Thhis polysig brought to you by Ian Burgmyer :)"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jaime Vives Piqueres's furious key-hammering produced this:
> Ah! I see.. That explains it all. POV reads the link file, and not
> follows the link to the real files... hmmm... I've never used links
> with POV: let me try.. It works fine here with the Linux version.
> Perhaps a problem with your custom compile?
Aliases in Mac OS might be implemented differently than symbolic links in Linux
and Windows NT. Maybe one of the Mac OS developers around here can answer
that... *nudges Chris and Thorsten* ;)
--
/*^*/light_source{100*<-5,2,-5>2}#macro I(i,n)#while(strlen(i)>=n)#local A=asc(
substr(i,n,1));#local a=asc(substr(i,n+1,1));cylinder{<div(A,8)-12,mod(A,8)-4,4
><div(a,8)-12,mod(a,8)-4,4>,0.1pigment{rgb z}}#local n=n+2;#end#end I("ScUe[]"1
/*<*/)I("mkmtlttk"1)//@_$#!,:<"Thhis polysig brought to you by Ian Burgmyer :)"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3e655440@news.povray.org>,
"Ian J. Burgmyer" <the### [at] mac com> wrote:
> Aliases in Mac OS might be implemented differently than symbolic
> links in Linux and Windows NT. Maybe one of the Mac OS developers
> around here can answer that... *nudges Chris and Thorsten* ;)
They are different, not quite like either symbolic or hard links. I
think they work this way: they contain a link to the actual file, so if
the file gets moved around, they stay attached to it. They also contain
the last location of the file, so if it gets deleted and replaced with
another, the alias points to the replacement. That way, aliases don't
break when files move around, and generally do what the user wants to do.
I don't know if/how POV handles them, though.
--
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <cja### [at] netplexaussieorg> ,
Christopher James Huff <cja### [at] earthlinknet> wrote:
> I don't know if/how POV handles them, though.
Unlike in Windos, in Mac OS and Unix, links (or aliases) are completely
transparent for applications. Thus there is no difference between them. Of
course, links (or aliases) can break. So it does make sense to check if
tehy are really valid. A user can do so using the Finder.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jaime Vives Piqueres <jai### [at] ignoranciaorg> wrote:
> On Tue, 4 Mar 2003 17:55:53 +0000
> kav### [at] delete_thisfocalimagecom (Kaveh) wrote:
>
> > Well, I put aliases to these files in the include directory, so as to
> > keep the files organized and separate. There was no error when reading
> > the 'include' command, so it saw the file, but did not *really* read
> > it, i.e. the declarations were not made. When I put in the files
> > directly into 'include', it worked.
>
> Ah! I see.. That explains it all. POV reads the link file, and not
> follows the link to the real files... hmmm... I've never used links
> with POV: let me try.. It works fine here with the Linux version.
> Perhaps a problem with your custom compile?
Could be. I don't know enough about the workings. My Linux friends
compiled it so everything works (except this maybe). Now I understand.
It doesn't understand the Mac alias pointing to the real file.
--
Kaveh
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Kaveh" <kav### [at] delete_thisfocalimagecom> wrote in message
news:1frbj3u.sqlop61bczl34N%kaveh@delete_this.focalimage.com...
>
> Could be. I don't know enough about the workings. My Linux friends
> compiled it so everything works (except this maybe). Now I understand.
> It doesn't understand the Mac alias pointing to the real file.
>
I'm missing something - I thought Mac used Linux now? (or do they use some
proprietary method to handle alias's? Why?)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 5 Mar 2003 12:59:32 -0000
"Tom Melly" <tom### [at] tomandlucouk> wrote:
> I'm missing something - I thought Mac used Linux now? (or do they use
> some proprietary method to handle alias's? Why?)
No, Apple uses now a Unix-based kernel (BSD). Linux is a Unix-like
system, wich is not exactly the same. I think they don't use clasic unix
links, but I'm still on my "first encounters" with Mac OS X, so I don't
know for sure.
--
Jaime Vives Piqueres
La Persistencia de la Ignorancia
http://www.ignorancia.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3e65f4b3$1@news.povray.org>,
"Tom Melly" <tom### [at] tomandlucouk> wrote:
> I'm missing something - I thought Mac used Linux now?
No, OS X is based on BSD.
> (or do they use some proprietary method to handle alias's?
Not really...they are the only ones who handle aliases. They serve a
similar purpose to links, but are not links.
> Why?)
Because they work better. There are web pages out there that go into far
more detail on this than I could.
--
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich's furious key-hammering produced this:
>> I don't know if/how POV handles them, though.
>
> Unlike in Windos, in Mac OS and Unix, links (or aliases) are completely
> transparent for applications.
Actually, all NT-based Windows versions support links for directories when using
NTFS. Microsoft, of course, chose not to give any good support for them (or
allow links to files). I think the only Windows NT release to actually make use
of NTFS links (which MS calls "junctions") are the Server releases. These
junction points are transparent to applications as well, but as I said before,
cannot be made without third-party software (stupidly enough...).
--
/*^*/light_source{100*<-5,2,-5>2}#macro I(i,n)#while(strlen(i)>=n)#local A=asc(
substr(i,n,1));#local a=asc(substr(i,n+1,1));cylinder{<div(A,8)-12,mod(A,8)-4,4
><div(a,8)-12,mod(a,8)-4,4>,0.1pigment{rgb z}}#local n=n+2;#end#end I("ScUe[]"1
/*<*/)I("mkmtlttk"1)//@_$#!,:<"Thhis polysig brought to you by Ian Burgmyer :)"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Christopher James Huff" <cja### [at] earthlinknet> wrote in message
news:cja### [at] netplexaussieorg...
<snip>
What really annoys me about win95/98 shortcuts to directories (I can't remember
if this is fixed under 2k/xp), is that you can't navigate using them if you are
trying to save a file. Windows just assumes you want to overwrite the .lnk file,
rather than go to the directory or file it points to.
f-ups set.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
