Memory Addresses in Hex

Bug #579340 reported by Debjit-bis08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnusim8085
New
Wishlist
Unassigned

Bug Description

It would be nice if memory addresses in the update memory
block are shown in Decimal & Hexadecimal as per user choice.

I have worked on this, got it to work ( bit buggy but not too bad.)

I dont have much experience in in practical world...
How can I contribute a patch ?

Tags: ui
Revision history for this message
Bug Importer (bug-importer) wrote :

Logged In: NO

Via the patch tracker, or alternatively via the mailing list. However the patch tracker is probably the preferred way.
Also, note that #1877050 has a related RFE which asks for the possibility to specify values in hex using a special notion, such as i.e. mvi a,20h

Revision history for this message
Bug Importer (bug-importer) wrote :

Logged In: NO

That's the patch tracker: http://sourceforge.net/tracker/?group_id=86462&atid=579701

Preferably, you post your patch there and discuss the details on the mailing list, otherwise people might not be aware of your patch, so that may end up being not committed or reviewed, as has for example been the case for some of the other posted patches.

Revision history for this message
Debjit-bis08 (debjit-bis08) wrote :

Logged In: YES
user_id=2042443
Originator: YES

#1877050 talks about different notation of numbers in the source code,
its related to the assembler
this is related to the gui.

Revision history for this message
Bug Importer (bug-importer) wrote :

yes, all addresses should be displayed in hex and dec - in fact, this should also be possible to specify for the "load at" field, where there's no mentioning of whether the value is to be provided in hex or dec, maybe there could be a dropdown menu in the same line providing "hex/dec" as choice

Revision history for this message
Bug Importer (bug-importer) wrote :

regarding hex immediates, this seems to be complicatd to fix (see http://sourceforge.net/tracker/index.php?func=detail&aid=2355581&group_id=86462&atid=579699), however you can avoid this bug by prepending a leading 0 to every hex immediate, for example:

mvi a,0FFh

while this is indeed somewhat redundant, it's at least one working way to still work with hex immediates. Maybe this restriction should be mentioned on the wiki or even be put in the documentation somewhere?

Revision history for this message
Debjit-bis08 (debjit-bis08) wrote :

I had submitted a patch (#1969360) for displaying the memory addresses and
contents in hex and also as a list.
Seems it was not reviewed.

Revision history for this message
Bug Importer (bug-importer) wrote :

I guess the key people behind the project are currently somewhat busy with their real lives, it appears there's lots of stuff going on at the moment, so I'd think we just need to be a little more patient, because there are simply not that many active developers at the moment.

Maybe this would change if they accepted some more contributors to the project, so that new contributors could get more easily involved, possibly by restricting their write access to a corresponding branch?

Generally speaking, I'd say this project could benefit from some more contributors-personally I'd say, if you provide a working patch that seems acceptable, you should be entitled to be actively involved in the project (if that's what you want).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.