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
Its not entirely clear how this should work yet - when different files have different data types defined etc. DiffWindow and DocumentCtrl will also need some rework to be able to vertically align the different regions in cases where they don't all have exactly the same height.
Requested by krisgnyc on Reddit.
The text was updated successfully, but these errors were encountered:
Not only do we have to deal with vertical alignment between the regions, which I was intending to solve by populating all the regions as normal, then splitting/divinding and adding padding as needed once each region had computed past the point where alignment was lost but could be corrected, we also need to worry about preserving correct alignment within regions (e.g. instruction boundaries) and not fucking that up when collapsing similar sections.
I'm thinking data type classes should be able to take a more active role in analysing files, and the results of that analysis could be stored in the Document and then queried by regions, so the disassembly and subdivision would be performed within Document once a range was set up as machine code (for example), and the DisassemblyRegion class would consult Document to know where instruction boundaries were.
Its not entirely clear how this should work yet - when different files have different data types defined etc. DiffWindow and DocumentCtrl will also need some rework to be able to vertically align the different regions in cases where they don't all have exactly the same height.
Requested by krisgnyc on Reddit.
The text was updated successfully, but these errors were encountered: