http://bugzilla.novell.com/show_bug.cgi?id=440101
User alexander.rettig@web.de added comment
http://bugzilla.novell.com/show_bug.cgi?id=440101#c37
Alexander Rettig changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexander.rettig@web.de
--- Comment #37 from Alexander Rettig 2009-07-12 14:40:38 MDT ---
I'd like to add to this issue from a *user's* point of view (I'm a developer
myself, but YAST2 is a tool for me, not a project ;-)):
First of all there are amongst others two possibilities I want to have when
working with the repositories module:
1) I want to have an obvious way to *select* a repository to view additional
information *without* changing any state of it
2) Maybe I want to have a fast possibility for activating and deactivating a
repository, but it's "only" albeit important convenience, if I need not to move
my mouse down to the "Enable" check box to change the activation state.
Possibility (1) is a *must* regardless of the chosen interaction style. I
myself am used to double clicks for "activating" items as e.g. icons in dolphin
or nautilus to run an application or open a file, but e.g. in the case of file
browsers (within an according interaction style) also using a single click for
that purpose is clear to me. It is not though in the case at hand: in my
opinion "enabling" a repository in YAST repository management has a
fundamentally different meaning than "activating" a file in the case of file
browsers. This becomes clear if you search the Qt signals of QTreeView for a
signal called "deactivated" - there is none! You cannot "deactivate" a file in
a file browser. The Qt signal "activated" has nothing to do with switching
on/off an "enabled" state (btw, it is not comprehensible to me as an user why
the "Enabled" state should be switched with principally different methods than
the "Automatically refresh" state). Thus regarding comments #22,#26 and #27:
yes, it's a YAST bug! The "activated" signal was abused, using the
"doubleClicked" signal is not only a workaround but a consistent solution (a
context menu would be even better though. Finanly a clear GUI solution also
would be if the "Activated" and "Autorefresh" check boxes simply were in
separate columns of the view. Then a single click on them had the obvious
meaning of changing the respective state and you could select a repository by
clicking on the text item of the row).
So, the reason why people (in the openSUSE 11.1 version) see YAST behave
strange may be the following: usually you configure your desktop experience as
a normal user, not as root. Thus maybe you (as I did) configure KDE to use
double click for activating icons. Then you run yast via the start menu, the
kdesu module comes in and makes YAST run as root - but you may not have
configured your root account to use double click for activation and thus only
in the YAST window you get KDE default behavior: single click = activated.
Voila...
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.