https://bugzilla.novell.com/show_bug.cgi?id=397292 User pilotgi@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=397292#c1 --- Comment #1 from kevin vandeventer 2008-06-04 16:32:33 MDT --- Maybe I should add that all the other specs are clickable and can be changed manually. It takes three separate steps in all, because after you change one, it takes you back to the hardware detection page. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=397292 User ms@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=397292#c2 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ms@novell.com |jdsn@novell.com --- Comment #2 from Marcus Schaefer 2008-06-11 07:06:14 MDT --- the sax2 gui adapts all these values but afaik the yast proposal does not change it automatically assigned to maintainer -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=397292 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- QAContact|jsrain@novell.com |sax2-maintainer-bugs@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=397292 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |jdsn@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=397292 User ms@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=397292#c4 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|ms@novell.com | --- Comment #4 from Marcus Schaefer 2008-09-08 01:32:55 MDT --- - The problem here is that the monitor couldn't be detected by its DDC id for some reason (maybe BIOS related) this information is missing. According to this libsax is not able to match the detected data with the static monitor database. So the monitor database includes an entry for the monitor but it can't be auto selected due to the the detection information - in sax2 when manually selecting an entry from the static monitor list not only the monitor name but also other information are adapted. The code which does this can be found here: api/monitor/monitormodel.cpp void SCCMonitorModel::slotName ( Q3ListBoxItem* item ) { ... } Jens Daniel the same implementation can be used inside the perl code for YaST. This is not a magic but is missing in the yast2-x11 code at least I didn't implement it - I intentionally did not change the resolution because people may want another resolution than the one we select. In times of no CRT monitors this could be change though because there are more and more screens which have one preferred and best resolution. I leave it up to you how to handle it in yast :)

Would it be better to fetch the resolutions to be offered from SaXManipulateDesktop::getResolutions(depth) insted of using a fixed list? Is this function intended for that use case?

The getResolutions() functions returns the resolutions per color depth this function can return an empty list you shouldn't use it to build the resolution list. There is a function called getResolutionsFromDDC1() which returns the DDC detected resolutions. You can use this one but I have disabled using it due to bug: #358346 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.