First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 145917
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Games <games@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Diego E. 'Flameeyes' Pettenò <flameeyes@gentoo.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
libsdl-1.2.11-xinerama-head-0.patch libsdl-1.2.11-xinerama-head-0.patch patch Diego E. 'Flameeyes' Pettenò 2006-09-01 16:45 0000 971 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 145917 depends on: Show dependency tree
Bug 145917 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-09-01 16:42 0000 
The attached patch applies over latest ~arch SDL version, and allows to use the
xinerama support to launch an application full screened on the head "0".

The SDL_VIDEO_FULLSCREEN_HEAD environment variable sets the head on which the
full screen will be displayed, but if you set it to 0, the code simply ignores
it as unset. My patch changes the unset value to -1, so that the 0 value can be
used correctly. Without this, trying to get fullscreen on head 0 would get the
same result than not having xinerama enabled at all.

I didn't send it upstream as I'm not sure if it's still an issue for them or
what else.

HTH,
Diego

------- Comment #1 From Diego E. 'Flameeyes' Pettenò 2006-09-01 16:45:40 0000 ------- 
Created an attachment (id=95696) [edit]
libsdl-1.2.11-xinerama-head-0.patch

------- Comment #2 From SpanKY 2006-09-03 19:06:17 0000 ------- 
upstream has rewritten a lot of the X stuff from scratch so i'll just keep it
in our ebuild

------- Comment #3 From SpanKY 2008-02-27 21:08:32 0000 ------- 
they rewrote the code for 1.3, but not 1.2 ... so i posted it upstream for 1.2
First Last Prev Next    No search results available      Search page      Enter new bug