https://bugzilla.novell.com/show_bug.cgi?id=679198 https://bugzilla.novell.com/show_bug.cgi?id=679198#c1 Ricardo Cruz <rpmcruz@alunos.dcc.fc.up.pt> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rpmcruz@alunos.dcc.fc.up.pt AssignedTo|bnc-team-screening@forge.pr |rpmcruz@alunos.dcc.fc.up.pt |ovo.novell.com | Severity|Normal |Minor --- Comment #1 from Ricardo Cruz <rpmcruz@alunos.dcc.fc.up.pt> 2011-03-13 20:12:27 UTC --- I agree there is space for improvement here. I completely disagree about it being an "usability abuse". The check-box works like everywhere else: on and off, if the package is installed. Inactive if the package is locked. (A tool-tip is even shown when the package is locked to make it clear.) This is the same approach used by PackageKit-gtk, the Mandriva software manager, and others. The design was an open process, and yours would be the first bug report about this part of the design (and this tool was already shipped as is back in 11.3). The look of the check-box depends on your gtk style. --- Where I'd agree there is room for improvement (if this is part of your complain) is that the check-box (like any other check-box) does not indicate change per se. You cannot know whether it was already 'on', or it has been changed. We do indicate whether the package has been changed by showing a yellow-ish background color. But in a software manager, we should probably do more than that: and indicate exactly what has been changed: particularly, if it's a version change. -- 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.