You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to discuss two QoL changes which would be nice to see implemented for code notes which have a large size attribute.
Currently, the logic tab associates addresses with a note if the address is less than the note address+size. For example, if I have a note at 0x100000 marked with [200 bytes], any addresses read from between 0x100000 and 0x1000c7 (inclusive) will be associated with that note in the logic tab. For example, if I use the address 0x10002d in an achievement, the note at 0x100000 will be associated with that address and [0x100000 + 41] will be shown at the top.
However, only decimal sizes are correctly parsed. For example, if my note instead used [0xC8 bytes] or [0xc8 bytes] instead of [200 bytes], those mid-note addresses, such as 0x10002D, will no longer show the note at 0x100000. Additionally, the offset shown in the note is in decimal (41 instead of 0x2d).
Therefore I would like to request that two changes be implemented:
Hexadecimal sizes are properly parsed, alongside decimal sizes. Large code notes are much more likely to use hexadecimal sizes as they are much easier to reason about in the hexadecimal address space.
The offset shown in the code note is shown as hexadecimal. Adding a decimal number to hexadecimal is confusing, and having both of these numbers be hexadecimal instead would make the math a lot clearer (and also likely make referencing hexadecimal offsets, if included on the code note, much faster).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'd like to discuss two QoL changes which would be nice to see implemented for code notes which have a large size attribute.
Currently, the logic tab associates addresses with a note if the address is less than the note address+size. For example, if I have a note at 0x100000 marked with
[200 bytes], any addresses read from between 0x100000 and 0x1000c7 (inclusive) will be associated with that note in the logic tab. For example, if I use the address 0x10002d in an achievement, the note at 0x100000 will be associated with that address and[0x100000 + 41]will be shown at the top.However, only decimal sizes are correctly parsed. For example, if my note instead used
[0xC8 bytes]or[0xc8 bytes]instead of[200 bytes], those mid-note addresses, such as 0x10002D, will no longer show the note at 0x100000. Additionally, the offset shown in the note is in decimal (41instead of0x2d).Therefore I would like to request that two changes be implemented:
Hexadecimal sizes are properly parsed, alongside decimal sizes. Large code notes are much more likely to use hexadecimal sizes as they are much easier to reason about in the hexadecimal address space.
The offset shown in the code note is shown as hexadecimal. Adding a decimal number to hexadecimal is confusing, and having both of these numbers be hexadecimal instead would make the math a lot clearer (and also likely make referencing hexadecimal offsets, if included on the code note, much faster).
Beta Was this translation helpful? Give feedback.
All reactions