FAQ
Cover
\
Build
\
Source
\
Bugs
\
Reference
\
Libraries
\
Tools
The bugs database has moved
here
.
Bug 666 : should there be a "noLights()" to complement lights()?
Last modified: 2007-11-01 05:21
P
roject:
processing
trash
Version:
unspecified
Co
m
ponent:
android
book
core
libraries
pde
reference
tools
web
Status:
RESOLVED
Resolution:
FIXED -
Pr
i
ority:
P2
Severity:
normal
Platform
All
O
S:
All
Windows
Mac OS
Linux
Other
Reporter:
davbol
Assigned To:
fry
Attachment
Type
Created
Size
Actions
Description
: Opened: 2007-10-29 14:56
(not a bug, possible feature addition, in response to Fry's status message)
For instance, if drawing GUI elements on top of a lit scene, might want to turn off
lights halfway through draw() when creating the GUI geometry. Currently can fake
this with "g.lightCount=0;", just wondering if you'd want something like "noLights()"
in the api.
Additional Comment
#1 From fry 2007-11-01 04:20
sure, i've added it in there for 0134, since it's also necessary to call
flush() so that geometry gets pushed out based on the current lighting
situation. we had wanted to keep things simple and leave it out, but i
don't want "g.lightCount = 0" to be the norm, especially when that will
break depth sorting.