http://defect.opensolaris.org/bz/show_bug.cgi?id=12917
Calum Benson <calum.benson at sun.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ue
--- Comment #3 from Calum Benson <calum.benson at sun.com> 2009-12-03 18:26:48
UTC ---
Hmm... this is quite hard to explain clearly, so bear with me :) (I should
probably just have drawn a picture...)
The intention of the UI spec is actually that the "Add to list of favorite
networks" checkbox in the "Connect to Wireless Network" dialog
(nwam-manager-properties -c) only applies to networks you join directly from
that dialog. But not to networks you join from other parts of the GUI, such as
the panel icon right-click menu.
That is, if I run 'nwam-manager-properties -c' and click the "Join Unlisted" or
"Connect" buttons, the "Join Wireless Network" dialog that pops up should
really have its "Add to list of favorite networks" checkbox hidden, because
I've already decided whether to add this network to the Favorites list. (The
UI spec doesn't currently specify that the checkbox should be hidden in this
case, however-- my fault.)
If I later right-click the NWAM icon and select "Join Unlisted Network", as in
Bob's example, the state of the "Add to list of favorite networks" checkbox in
that dialog isn't really intended to be the same as it was in the "Connect to
Wireless Network" dialog. (Although again, the UI spec doesn't currently
specify what it *should* be-- probably either (a) the same as it was the last
time you closed this dialog, or (b) always checked by default).
So I think, in fact, the GUI is behaving as the spec intended. However, from
Bob's report, the intended behaviour is perhaps not clear.
I'm wondering, therefore, would it be clearer/simpler if we just removed the
checkbox from the "Connect to Wireless Network" dialog, and always showed it in
the "Join Wireless Network" dialog?
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
