| Summary: | Add additional decoding of 16, 32, and 64-bits on left-side | ||
|---|---|---|---|
| Product: | [Applications] okteta | Reporter: | Aaron Williams <aaronw> |
| Component: | general | Assignee: | Friedrich W. H. Kossebau <kossebau> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version First Reported In: | 0.26.6 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Aaron Williams
2022-02-25 10:35:28 UTC
> It would be nice if the data could be displayed as groups of 16, 32, or 64-bits on the left-hand side rather than clicking on the right to see the decoding table with options for little or big endian. With "left-hand side", you mean the byte value display (with the options binary, octal, decimal, hexadecimal)? And with "right" the character display? What do you mean exactly by "clicking on the right"? After all the decoding table also adapts to the cursor when placed/moved in the byte values view part? What exactly do you mean by "groups of 16, 32, or 64-bits" or "32 or 64-bit values"? Integer values? If so, curious what use-case there is to combine view of 8-bit character set with mult-byte integer values? Would one not rather want to combine the single byte value (as the most common notation/interpretaion of the 8 bits of a byte) with whatever special data type those bytes are used for to encode? Can you give a visual mockup how you would like to see the display done, and perhaps give a sample of the use-case you have? So far I understand your request is a variant of bug 214131, just with multi-byte integer values instead of float or double? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |