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
color issue in Processing3.0b1
Hi,
I'm getting an error each time I want to use the color class.
when instanciating a color I have an error saying 'The class "color" does not exist'
In the console there is the following:
color type detected This shouldn't be happening! please report this as an issue
In the errors there is a suggestion of importing the java.awt.Color class but that seems to be a bit exessive
Anyone now what is going on?
Answers
the color type is a bit odd. it's not a class, it's actually a synonym for int, one that gets replaced during the pre-processing phase before compilation.
the above seems to suggest that the preprocessing isn't working as it should and 'color's are remaining in the code that gets compiled.
importing java.awt.Color isn't the way to fix this, it will just confuse things futher.
post the a small, runnable code sample that shows the problem - there may be a syntax error somewhere else that's showing up as this. at the very least we'll be able to narrow it down to a problem with the version of processing you're using.
ok, that makes sense, my mistake was instanciate it as a class using 'new' sorry for being such a noob in this but the console wasn't really helpfull telling me to report it as an issue :-)
@Ilumen, you have specifically mentioned that it happened in Processing 3.0b1 beta.
It automatically implies that it would work on older stable versions! :-@
Another hint: when you have a problem, try and show a few lines showing what you tried to do... koogs was good at guessing, but it can just be a waste of time in most cases.