What steps will reproduce the problem?
1. "Sign In" and "Sign Out" are two sides of the same coin - it's a toggle of
the same state.
2. The buttons are currently quite far away, even though they are closely
related.
3. Combining them saves space, relates them in the closest possible way and
visually conveys their nature as a toggle of the same state.
What is the expected output? What do you see instead?
Related buttons should be near each other. Toggles should be controlled from a
single button. Currently, the toggle is created with two buttons that are not
near.
What version of the product are you using? On what operating system?
GH 1.537k (bm branch)
Please provide any additional information below.
1.537bm already turned the top buttons into a control array. The array index
values are set up as an ENUM. This means the buttons could share the same array
index quite easily.
A bit of logic would need to be added, to decide which action to take when the
button is clicked. The login state is already tracked in a Form-level Boolean,
IIRC.
Original issue reported on code.google.com by aa22c...@gmail.com on 22 Apr 2012 at 1:17
Original issue reported on code.google.com by
aa22c...@gmail.comon 22 Apr 2012 at 1:17