-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor/hexview #427
Refactor/hexview #427
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some outstanding issue that should be fixed before this can be merged.
- Likely due to
Pane
refactor, this PR removes padding all over the GUI that should be fixed - The search bar in the tree view is no longer pinned to the top, and scrolls away when you scroll the tree
- The minimap now floats half way between the right of the hex view and the right of the screen when it should be pinned to the right of the screen
- The minimap no longer takes up the full height of the screen, which makes it less practical to use, less easy to see details, etc.
- The minimap and "go to offset" input no longer have a black background, and the hex can be seen around/behind them if the hex area is thin enough to cause overlap
- The "breadcrumb" that used to be at the top of the hex view is no longer visible (it does seem to come back in the disassembly view for some reason)
- The hex view does not allow scrolling past the bottom when using the scroll wheel – I know there is a comment in the code that this is a bug, but I actually ended up kind of preferring it this way
- Scrolling with the mini map does not round to the nearest line correctly (see video at the bottom)
- The bottom of the red "view window" in the minimap is not opaque
- Scrolling in the disassembly view no longer works
- Scrolling in the text view no longer works
Scrolling not working right:
Screen.Recording.2024-02-23.at.2.03.08.PM.mov
Left button bar lack of background:
![image](https://private-user-images.githubusercontent.com/99368685/307426345-cf19ab7e-1b45-4a3b-b7d6-cf65d993180a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk0NTQyNjQsIm5iZiI6MTczOTQ1Mzk2NCwicGF0aCI6Ii85OTM2ODY4NS8zMDc0MjYzNDUtY2YxOWFiN2UtMWI0NS00YTNiLWI3ZDYtY2Y2NWQ5OTMxODBhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEzVDEzMzkyNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTFjZjgyNTBlMTg4NDkxZjE5MDRiY2JiM2ExNzcyYmIyN2JkYzhlMTlkNmMzMzk4YjNjMzgxNmUzZWRkOTZmODkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.lZ_AuNTp8UXLOyfoKeQvDYXsuujBoSV1IhaykOibINk)
Minimap needs background, and should be full height:
![image](https://private-user-images.githubusercontent.com/99368685/307426472-db569519-7a6b-4b8d-abad-c4f7f76be382.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk0NTQyNjQsIm5iZiI6MTczOTQ1Mzk2NCwicGF0aCI6Ii85OTM2ODY4NS8zMDc0MjY0NzItZGI1Njk1MTktN2E2Yi00YjhkLWFiYWQtYzRmN2Y3NmJlMzgyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEzVDEzMzkyNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWIyMjRhMmVhM2QxMjA3ODk4NmFjODk1YjU4Y2RjNDMxOTFmMDNjY2MzYjRkMDgyODEyYWMyY2FlYTNjYTk0ZTAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.jM2XjzqbVwjUjUHrgkjGhs8zqNnbbEk-obiAi0IdJbc)
Co-authored-by: Jacob Strieb <[email protected]>
Co-authored-by: Jacob Strieb <[email protected]>
Co-authored-by: Jacob Strieb <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Edge case that may not be worth worrying about, but the minimap gets cut off if the hex view gets too small.
Screen.Recording.2024-02-26.at.4.01.04.PM.mov
Co-authored-by: Jacob Strieb <[email protected]>
Co-authored-by: Jacob Strieb <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One additional observation about the pane changes is that the vertical and horizontal scrolls are handled differently in a way that I think is potentially confusing for a user. Specifically: there are horizontal scroll bars, but they're way at the bottom and can go out of view. Also if you middle click in the tree with the mouse wheel, it only lets you scroll horizontally.
Similarly, horizontal scrolling the hex view doesn't work if it's too small.
I've included a video, but I don't consider fixing the horizontal scroll critical for this PR. If it's an easy fix, we should do it. But it shouldn't block the PR getting merged.
Screen.Recording.2024-02-27.at.5.37.07.PM.mov
Horizontal scrolling here would be a bit weird, I think the best solution would be to adjust the alignment size based on the hexview element width. In the interest of time, i think this should be a separate PR. |
I'm more concerned about horizontal scrolling in the tree view being weird than about not being able to horizontally scroll the hex view. The only reason I bring them up together is that I think they're likely related. Like I said, no need to block this PR on that. |
Not related, the hex view doesnt "scroll" so i have scrolling totally turned off for that view, if I enable it, it does the "double scroll" that initiated this entire PR. Regardin the resource view, easy fix, theres an |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for all of the revisions. Looks good to me! 🤑
--------- Co-authored-by: Dan Pesce <[email protected]> Co-authored-by: Jacob Strieb <[email protected]>
One sentence summary of this PR (This should go in the CHANGELOG!)
Link to Related Issue(s)
Please describe the changes in your request.
Anyone you think should look at this, specifically?