eclipse-cdt-cloud / eclipse-cdt-cloud/vscode-memory-inspector
Memory Inspector display enhancements
- Dominant language
- TypeScript
- Stars
- 17
- Forks
- 25
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 8
Description
**Description**
As discussed during the last CDT Cloud meeting, I'd like to share some thoughts on potential display enhancements which could make the Memory Inspector even more powerful than it is already today.
- [x] https://github.com/eclipse-cdt-cloud/vscode-memory-inspector/issues/62 (show/hide radix prefix, change radix)
- [ ] #118
- [x] #73
- [x] #74
- [x] #75
- [x] #76
- [x] An extension point for more CPU architecture specific representations, e.g. special floating or fixed point formats. Covered by #77?
- [x] Selectable word endianess, for example if viewing a memory buffer for a peripheral which operates with a different endianess than the CPU. Covered by https://github.com/eclipse-cdt-cloud/vscode-memory-inspector/pull/93
- [x] Show most common formats for a selected word in a separate area. Covered by https://github.com/eclipse-cdt-cloud/vscode-memory-inspector/pull/87
- ~~Configuration of physical access size in bytes. (Understood that currently not supported by MS-DAP). TODO: move to separate issue, out of scope for this one here due to dependency to MS-DAP updates.~~ Moved to separate issue #104
**Additional information**
Contributor guide
Assessment
This issue has not been assessed yet.