openframeworks / openframeworks/openFrameworks
Settings.screenNum ignored when using ofAppEGLWindowSetting
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
My issue is when I want to create an output window on the hdmi output by using this code :
`int main( ){
ofAppEGLWindow::Settings settings;
settings.width = 400;
settings.height = 480;
settings.setPosition(ofVec2f(0,0));
settings.screenNum = 5;
ofCreateWindow(settings);
ofRunApp( new ofApp());
`
The window appears on the LCD display and not the hdmi output.
I placed an oflognotice in the ofAppEGLWindow.cpp, line 394, in the ofAppEGLWindow::setup(const Settings & _settings) and it returns 0 as its setting.screenum value.
I use a RPI 2 with oF 0.9.0
I posted about it in the forum
Regards.
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
Inspect ofAppEGLWindow.cpp around line 394 and the ofAppEGLWindow::setup(const Settings&) entry point, using the supplied ofCreateWindow example on an RPI 2 with oF 0.9.0. Verify how settings.screenNum is received and whether the window is placed on the HDMI output rather than the LCD display.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, raspberry-pi
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100