|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2-x11: Remove linkage between x11/console mouse setup from "yast2 mouse" module and rename "yast mouse" to "yast gpm" module | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Markus Elfring <Markus.Elfring> |
| Component: | YaST2 | Assignee: | J. Daniel Schmidt <jdsn> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Enhancement | ||
| Priority: | P3 - Medium | CC: | forgotten_EGKOvZW2-J, jdsn, ms, sndirsch |
| Version: | unspecified | ||
| Target Milestone: | Alpha 0 | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Markus Elfring
2008-12-27 08:00:19 UTC
Thanks for your report. The reason why the lists are different in the text UI and graphical UI is, that when started from a GUI YaST will call SaX2 directly (external program). In case of textmode yast will start a small mouse configuration (YaST) module which only knows about a subset of devices and does not rely on SaX2 (so it can be installed independently). Stefan, Marcus: Does it make sense to regularly export/sync the mouse devices list from the SaX2 database to the mouse_raw.ycp file? (meaning, I do a sync prior to a release - I don't want to sync this stuff on installed systems). Or is there a specific reason why the mouse_raw.ycp database only knows about a small subset of mice? I move this to openSUSE 11.2. Honestly. I don't know where these come from. :-( The reason for this is because yast2 mouse has been written to setup the console mouse in other words the gpm mouse. The yast2 mouse module additionally adapts the first (core pointer) input device section from the X configuration with the selection made in the yast2 mouse module. From a todays perspective this might not be a good design anymore because the core pointer functions in X often are way beyond the capabilities of the console mouse my suggestion is to remove the linkage between console and X11 mouse from the yast2 mouse setup and maybe also rename yast2 mouse into yast2 gpm or something Thanks for details explanation, Marcus. Your proposal makes perfect sense to me. BTW, it's rather likely that the SaX2/YaST X11 mouse module will vanish completely. See Bug #483554 why. (In reply to comment #5) > BTW, it's rather likely that the SaX2/YaST X11 mouse module will vanish > completely. See Bug #483554 why. Which is currently happening ... (In reply to comment #6) > (In reply to comment #5) > > BTW, it's rather likely that the SaX2/YaST X11 mouse module will vanish > > completely. See Bug #483554 why. > > Which is currently happening ... done. Jens-Daniel, could you take care of this one for openSUSE 11.2? If possible already for Milestone 4. I made the adaptions and submitted a package. But I did not rename the module itself, only the title in the Control Center. Will do the full renaming after my vacation. Lowering priority. *** Bug 524780 has been marked as a duplicate of this bug. *** Any schedule for the renaming part available? Only the desktop file got a new title: GPM Configuration. The package itself didn't get renamed (yast2-mouse is a good generic name, why rename it for the sake of renaming). And of course it will never call sax2 again but only configure GPM. Find the latest version here: https://build.opensuse.org/package/show?package=yast2-mouse&project=YaST%3AHead A submit-request to openSUSE:Factory has been created. Thanks a lot! |