Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
Possible noFill() bug in P3D/Processing 2.2.1
I am using the P3D renderer in Processing 2.2.1 in HSB color mode.
I make a noFill() call to render some shapes without fill. I then want to black out the screen, so I call fill(359,100,0) followed by rect(0,0,width, height), yet nothing happens. If I remove the call to noFill(), the black rect renders as expected, and blacks out the screen. Additionally, if I switch my renderer to P2D, it also works as expected. Only in P3D does it fail to render the rect.
It seems like maybe this could be a bug in the P3D implementation and some glEnable calls, but that's just a guess. Anybody have a similar experience, or see something I'm doing wrong that's incompatible with P3D?