Improper execution order of keybinding selectors, with regard to "toggleFilterKey:"
Reported by Zvi Biener | June 21st, 2018 @ 01:40 PM
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.
Comments and changes to this ticket
-
benny July 18th, 2018 @ 12:31 PM
- State changed from “new” to “fixcommitted”
-
benny July 18th, 2018 @ 12:33 PM
I guess for a key binding like this one then you would also like me to add
setFilterKey:(andremoveFilterKey:)? Toggling is a bit unpredictable. -
Zvi Biener July 18th, 2018 @ 01:52 PM
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.
-
Zvi Biener July 25th, 2018 @ 12:28 PM
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.
-
-
-
benny September 10th, 2018 @ 02:03 PM
- State changed from “fixcommitted” to “fixreleased”
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.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Mac OS X email client.
benny