Anonymous | Login | Signup for a new account | 2019-02-20 01:37 UTC | ![]() |
Main | My View | View Issues | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0000755 | EMStudio | User Interface | public | 2012-11-02 16:14 | 2012-11-02 22:42 | ||||
Reporter | malcom2073 | ||||||||
Assigned To | malcom2073 | ||||||||
Priority | normal | Severity | feature | Reproducibility | always | ||||
Status | closed | Resolution | won't fix | ||||||
Platform | All | OS | All | OS Version | All | ||||
Product Version | ASAP | ||||||||
Target Version | 0.0.1 | Fixed in Version | |||||||
Summary | 0000755: Right click menu in Tunable Memory display should allow user to see either Hex view, or "standard" view | ||||||||
Description | Right now, if there is a handler for a particular locationID, it is used. Be it a 3d table 2d table, configuration, whatever. This issue is to keep the default behavior the same (double click opens with the default handler), but allow for a right click menu so a user can view/edit anything they want in hex. For instance, if something is not working properly for editing in the display handler, they can revert to hex and edit it. | ||||||||
Tags | No tags attached. | ||||||||
Issue Type | New Feature | ||||||||
Attached Files | |||||||||
![]() |
|
![]() Fred (administrator) 2012-11-02 16:25 |
Provided it remains rebased on the HEAD of unstable at all times, and NEVER sees the light of day in any other branch/commit/release, it's fine. Otherwise it's fucked. |
![]() malcom2073 (manager) 2012-11-02 22:32 |
Fred doesn't want it, Fred won't get it. I'll have it on mine, but if he thinks no other user needs it then it doesn't need to be in the repo at all. |
![]() Fred (administrator) 2012-11-02 22:41 |
Fred doesn't matter, it's your app. Fred just doesn't want dumb users exposed to the ability to cut off their feet. I've put as many checks in place on the firmware side as I reasonably can to guard against bad tuning data (as you and Dave both have found out during dev, it works well), but I can't fully protect them from my end. That must be done in the app they're using through robustness, reliability and good semantics. I totally understand the desire to switch to hex while hacking on stuff, however immediately afterward was the time to fix the widget that had failed you, and implement checks to ensure it can't happen again, not to implement an "avoid fucked widget" feature. I hope that makes more sense and isn't emotive. |
![]() Fred (administrator) 2012-11-02 22:42 |
...fix the widget that failed you, or add that resize feature that you needed, etc. |
Copyright © 2000 - 2011 MantisBT Group |