-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Mark Many... excludes last byte. #38
Comments
documenting my own actions..... That all works correctly, but, Yes, it does seem a little counterintuitive from a UX standpoint that the last number you enter isn't included in the range, even if the action performed is correct. Seems like a decent improvement would be to make the labels be "Start at Address" and "Up to AND INCLUDING address". That would look like this: If you enter the same address (0xC43842) in both boxes, the #bytes will say 0x01 byte count I needed to mock this up just to get my head around it, so here's what it looks like if you entered: enter: start @ 0xC00010 I think that makes a bit more sense intuitively, since users are more likely to enter the starting address and # of bytes, and have the form calculate the rest. When it does, the second ending number will reflect something actually being marked and not "one beyond" that. I'm going to sleep on this but good with implementing this change if no one else objects |
- from #38 - backport interfaces and code from v3.0 branch
fixed in master branch, next build will have this |
Marking C43842-C43843 will only mark C43842 with the indicated label.
The text was updated successfully, but these errors were encountered: