@cancel I'm not sure if I'm totally in love with this, it creates all sorts of little side effects, like editing is weird, mouse picking is weird, I might keep it like
LIT2
01
23
And somehow display the body of the literal differently.
Top-level
@cancel I'm not sure if I'm totally in love with this, it creates all sorts of little side effects, like editing is weird, mouse picking is weird, I might keep it like LIT2 And somehow display the body of the literal differently. 3 comments
@neauoire I don't think I can collapse them into one line without adding a bunch of code, because right now it just maps one address/byte -> one line. but I could make it display both, primarily the one-line version on the first line, with the raw opcodes/bytes greyed out on the first and second lines. @cancel yes! that's a good idea. I've had to jump through the hoops to increment the line id too, it's the part of that display mode that irks me the most. A fully formatted value on the first LIT byte would be ideal. |
@cancel actually, yes, beetbug should display it like this. It's very nice when looking with code side by-side and see the exact same formatting. I think if there aren't too many editing side-effects, if you can, you should make it display on a single line.