|
Bugzilla – Full Text Bug Listing |
| Summary: | Unexpected look-and-feel for YaST+Gnome | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Johannes Meixner <jsmeix> |
| Component: | YaST2 | Assignee: | Michael Meeks <mmeeks> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | forgotten_h13THG8RK1 |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Patch to fix the manufacturer immediate selection
Same as before with spacing fixed (don't exceed 80 chars in a line) |
||
|
Description
Johannes Meixner
2007-08-24 09:58:29 UTC
By the way: During abort or finish of the YaST printer module, there is a gtk warning: --------------------------------------------------------------------------- caps:~ # yast2 printer & [1] 17231 caps:~ # (gtk:17256): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (gtk:17256): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() [1]+ Exit 16 yast2 printer caps:~ # --------------------------------------------------------------------------- I get various other such Gnome and gtk warnings and have various strange effects (e.g. black text on black background) so that I assume it is a general YaST+Gnome problem but perhaps it is all intentionelly? We do have a yast2-gtk-ui now. The general idea behind is that it should integrate better with the GNOME desktop. That includes look & feel as well as user interface policies. I don't know if that double-click behaviour you described is intentional. I would also consider this very odd. Michael? Created attachment 164155 [details]
Patch to fix the manufacturer immediate selection
I'm not sure why the Qt stuff is already working. Perhaps the default in a Qt selection box is to activate? In any case, the printer's default.ycp code did not specify the "immediate" option, which this patch fixes. This patch does not affect Qt's printer selection; it works just like it did before.
Created attachment 164159 [details]
Same as before with spacing fixed (don't exceed 80 chars in a line)
UI event reference doc: http://forgeftp.novell.com///yast/doc/SL10.2/tdg/UI-Events.html A SelectionBox sends a ValueChanged event with `opt(`notify) in the Qt UI and with `opt(`notify, `immediate) in the NCurses UI. The rationale for this difference was IIRC that unlike in a graphical UI, you cannot jump from one item to another without selecting each item between them. In a GUI, you can do that with the mouse. I am not sure, but it might be that the Gtk-UI behaves like NCurses here. IMHO it would make sense to make it behave like the Qt UI. Johannes, you could verify this by adding `immediate. I added the current maintainer of yast2-printer to CC. Hey Johannes, yeah, this is a bug. I'm afraid this went to 10.3, but its fixed on SVN. About the other problems, I can't reproduce them, so I would need some information. At what point do you get the Pango warnings? And run the printers tool, from the following command, sending us the output: /usr/lib/YaST2/bin/y2base -l /dev/stdout 2>&1 printer gtk > log About the black-on-black glitch, send us a screenshot, if you hit the problem again. Thanks. I cannot provide more information. It happened during installation of a 10.3 beta version. Meanwhile I use (as usual) KDE on my machines. Alright. The reported bug is fixed anyway. For the next release, I will checkout the Gnome cd... *** This bug has been marked as a duplicate of bug 332384 *** |