Skip to content
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

Enhancements: Memory editor #357

Open
DHLF opened this issue Oct 25, 2019 · 1 comment
Open

Enhancements: Memory editor #357

DHLF opened this issue Oct 25, 2019 · 1 comment
Labels

Comments

@DHLF
Copy link

DHLF commented Oct 25, 2019

When using the hex memory viewer/editor I noticed the fixed size of the window.
This is somehow slightly annoying.
At least double height would help a lot if it has to be fixed.

Also the size of the editable memory seems sometimes not large enough(scrolling back/forward seems to be limited to a fixed size).
This happens even if the memory contains continueing data.

It may be that due to the memory management(pages??) used by linux it is too difficult to keep up with which part continues where..

The last(and most important wish err.. suggestion):
If in the lower part of the memory viewer window the actual cursor address contempt is also shown as word/long/float(or let us select which ONE of them has to be shown instead of all possible value types) this would speed up memory examination a lot.

In spite of typical conventions it would be okay if the values are even shown on ODD cursor addresses(as few games store stuff this way to hide values(and it were recent games!)).
So it would be up to the user to place the cursor on even addresses if this is his intention.

Sorry for just asking for improvements instead of helping coding.

@DHLF
Copy link
Author

DHLF commented Oct 28, 2019

After a brief look over the hexview.py file I have to admit that python is NOT my cup of coffee.
Few parts looks familar but most of the code seems "alien" to me.

So I would(if i ever would be able to..) try first to change the background colour to mark the first four bytes in normal, the second four bytes in grey and so on.
Just to make reading all those values easier.

Second I would like to try to add the display of any value(which is marked by the cursor) for bytes, words and long words aka int32 in decimal.
Problem:
Where to put it? On the lower part of the window?
Should it be shown only on demand or always?
Should the cursor movement and so the calculation be fixed(one step for bytes, 2 steps for words, 4 for in32?) or not?

Is the "layout" of the hexview.py window stored separately? (where all the buttons goes)?
YES->GameConqueror.ui seems to define all those user-interface-stuff.
There MUST be some kind of editor for this.
->glade(search engine: gtk editor or look at the second line of GameConqueror.ui :D )

Now I have to play around with glade a bit to add those "buttons" where the values shall be shown.
I decided to use one "button" for each calculated value.
Just some names for those "button" things: calc8, calc16, calc32 should do for the moment.
Next step would be to fill those "buttons" live with values.
I am sure i will miss proper declarations -.- but its bedtime..

@bkazemi bkazemi added the GUI label Sep 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants