![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Tool bars
- ability to select which toolbars to show and which to hide
- on the main button toolbar, show/hide text under icons (auto adjust height
to match)
- loose the sparkly spheres image?
Includes
- Make the includes path recursive, so any files in a sub dir of the
includes path are found
--
Rick
Kitty5 NewMedia http://Kitty5.co.uk
POV-Ray News & Resources http://Povray.co.uk
TEL : +44 (01270) 501101 - FAX : +44 (01270) 251105 - ICQ : 15776037
PGP Public Key
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x231E1CEA
---
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.404 / Virus Database: 228 - Release Date: 15/10/2002
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> - Make the includes path recursive, so any files in a sub dir of the
> includes path are found
I agree. The only problem with this would be duplicate filenames in
seperate directories, for example "texture.png" might crop up more than
once, leading to confusion if you didn't remember this. But that's a
small inconvenience compared to the benefits.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Sun, 20 Oct 2002 21:12:12 +0100, Andrew wrote
>> - Make the includes path recursive, so any files in a sub dir of the
>> includes path are found
>
> I agree. The only problem with this would be duplicate filenames in
> seperate directories, for example "texture.png" might crop up more than
> once, leading to confusion if you didn't remember this. But that's a
> small inconvenience compared to the benefits.
I disagree. Guess why C compilers do not have recursive include
paths. And C exists since the 1970s, and an awful lot of software has
been written in it, so if recursive include paths would actually have
any benefits the compiler people would have introduced them a long time
ago. Since they didn't there must be something wrong with that concept.
To conclude, I think it would be a bad idea to do this for POV-Ray. The
least would be to make it optional.
--
Timon Christl <me### [at] christltimon de>
AIM: sgmfragcollector
ICQ: 172280602
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <3db3e40d$1@news.povray.org> , Timon Christl
<chr### [at] nakatcha fmi uni-passau de> wrote:
> I disagree. Guess why C compilers do not have recursive include
> paths. And C exists since the 1970s, and an awful lot of software has
> been written in it, so if recursive include paths would actually have
> any benefits the compiler people would have introduced them a long time
> ago. Since they didn't there must be something wrong with that concept.
??? Maybe the compiler you are using does not support recursive search for
include files, but that does not imply no other compilers offer it as an
option...
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trf de
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <3db3e40d$1@news.povray.org>,
Timon Christl <chr### [at] nakatcha fmi uni-passau de> wrote:
> I disagree. Guess why C compilers do not have recursive include
> paths. And C exists since the 1970s, and an awful lot of software has
> been written in it, so if recursive include paths would actually have
> any benefits the compiler people would have introduced them a long time
> ago. Since they didn't there must be something wrong with that concept.
"C compilers don't have it so it's bad"...do I have to tell you how
faulty that reasoning is?
--
Christopher James Huff <cja### [at] earthlink net>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tag povray org
http://tag.povray.org/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Rick [Kitty5] <ric### [at] kitty5 com> wrote in message
news:3db302d7@news.povray.org...
>
> Includes
> - Make the includes path recursive, so any files in a sub dir of the
> includes path are found
>
I read these threads whenever they come up. This is the first one I've seen
in a while that looks really exciting and useful.
-Shay
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Rick [Kitty5]" <ric### [at] kitty5 com> wrote in
news:3db302d7@news.povray.org:
> Tool bars
> - ability to select which toolbars to show and which to hide
> - on the main button toolbar, show/hide text under icons (auto adjust
> height to match)
> - loose the sparkly spheres image?
>
> Includes
> - Make the includes path recursive, so any files in a sub dir of the
> includes path are found
>
>
I'll join this wishfull thinking
System Tray Icon
- Add pause/resume rendering to right click menu
I know, I know...
"If you really want this, then code it yourself"
;)
Tom
The C Klutz
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |