openframeworks / openframeworks/openFrameworks
ofImages loaded via ofLoadImage don't draw
Open
Nobody has claimed this yet.
bug
core
section-2D
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
0072 Develop, OS X 10.8
which is different than image.loadImage behavior
Test case
ofImage loadImage;
ofImage image;
//--------------------------------------------------------------
void testApp::setup(){
string imagePath = "imageTest.jpg";
ofLoadImage(loadImage, imagePath);
image.loadImage(imagePath);
}
//--------------------------------------------------------------
void testApp::update(){
}
//--------------------------------------------------------------
void testApp::draw(){
loadImage.draw(0, 0);//[warning] ofGLRenderer::draw(): texture is not allocated
image.draw(0, 0);//draws
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the supplied test case on OS X 10.8, comparing ofLoadImage(loadImage, imagePath) with image.loadImage(imagePath). Trace why loadImage.draw(0, 0) reports an unallocated texture while image.draw(0, 0) succeeds; done when both loading paths draw the image without the warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100