https://bugzilla.novell.com/show_bug.cgi?id=397292
User jdsn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=397292#c3
J. Daniel Schmidt changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |ms@novell.com
--- Comment #3 from J. Daniel Schmidt 2008-09-05 10:56:21 MDT ---
The values yast2-x11 shows in the proposal are directly from sax2. There was
some miscalculation that is fixed now for 11.1.
It would be great to get the logs from your installation, where this detection
fails _and_ later in the installed system works. I guess you no longer have the
logs of the installation of openSUSE 10.3. But maybe you might want to try to
install openSUSE 11.1 beta1 or beta2 once they are out and report back. Thanks
in advance.
Marcus:
- Is there any magic I need to add here to let SaX adjust the settings
automatically if the monitor vendor/model changes? For the proposal the
settings that are displayed are updated on any change that is done in the
proposal - values are fetched directly via XLib (via getActiveResolution). So
how do I tell SaX to use the best settings according to the new monitor model.
- 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 drawback is that a missing resolution (in the list) or a misdetected
setting changes this list would confuse the user as he can no longer set the
best resolution. But I see the need to have this coupled somehow.
--
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.