Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Improper execution order of keybinding selectors, with regard to "toggleFilterKey:"

#2034

When '"toggleFilterKey:", "unread"' is added to a keybinding, the corresponding actions seem to be executed before those that precede them.

Example:

"n" = ("selectNextCountedMailbox:", "toggleFilterKey:", "unread");

This toggles the filter on the current mailbox, then changes mailboxes. Instead of the intended order.

Reported by Zvi Biener · June 21st, 2018 @ 01:40 PM

State: new
Milestone: none
Assigned to: benny benny

Activity

  1. benny
    benny
    • State changed from new to fixcommitted

    July 18th, 2018 @ 12:31 PM

  2. benny
    benny

    I guess for a key binding like this one then you would also like me to add setFilterKey: (and removeFilterKey:)? Toggling is a bit unpredictable.

    July 18th, 2018 @ 12:33 PM

  3. Zvi Biener
    Zvi Biener

    Thanks! I guess those would be useful bindings, but really, I'm fine just using the unread key. (If I understand how this works). No need for more work for you.

    July 18th, 2018 @ 01:52 PM

  4. Zvi Biener
    Zvi Biener

    My last comment clearly shows I misunderstood what you meant. I finally came around to implementing this, and now I understand. Yes, a setFilterKey: (and removeFilterKey:) would be great. But, again, negligible priority. I'm probably the only person interested.

    July 25th, 2018 @ 12:28 PM

  5. benny
    benny

    Well, they exist in the next update.

    August 9th, 2018 @ 01:15 PM

  6. Zvi Biener
  7. benny
    benny
    • State changed from fixcommitted to fixreleased

    September 10th, 2018 @ 02:03 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.