mirror of
https://github.com/fadden/6502bench.git
synced 2024-06-26 11:29:33 +00:00
Added some feature requests from the issues list
parent
3a648a7a0e
commit
a8b1977079
|
@ -144,6 +144,8 @@ Contents:
|
|||
* Streamline instruction operand editor: don't open a separate dialog
|
||||
to edit a line label. Maybe just show the operand target line and
|
||||
invite them to update the label in place?
|
||||
* Add a feature to quickly format "LDA #<lo / LDA #<hi" situations.
|
||||
See https://github.com/fadden/6502bench/issues/120 (related: #21)
|
||||
* Improve the "find" feature. Case-sensitivity, regex, incremental
|
||||
searching, "you have wrapped" dialog disable. Normalize string
|
||||
delimiters so searching for "'A'" finds 'A', "A", ‘A’, etc.
|
||||
|
@ -163,6 +165,7 @@ Contents:
|
|||
* The data operand editor should allow arguments other than hex for
|
||||
the data argument in "fill" operations, e.g. ".fill 80,'*'" for a line of
|
||||
asterisks. Would also be good to allow hex for the count argument.
|
||||
See https://github.com/fadden/6502bench/issues/116
|
||||
* Make the data operand editor a bit smarter about selecting appropriate
|
||||
defaults when formatting strings. Add a shortcut to make selection
|
||||
and formatting of strings easier.
|
||||
|
@ -359,7 +362,8 @@ Contents:
|
|||
something that would happen as part of asm generation, not in the
|
||||
on-screen code list.
|
||||
* Multi-source output. Large projects should be generated into multiple
|
||||
source files.
|
||||
source files. Breaking them apart at top-level address region boundaries
|
||||
should yield good results. See https://github.com/fadden/6502bench/issues/115
|
||||
* Expand per-assembler output options.
|
||||
* Make operand wrap length configurable.
|
||||
* Consider making options like upper/lower case and label localization
|
||||
|
@ -423,6 +427,7 @@ Contents:
|
|||
pull in optional symbol files and extension scripts.
|
||||
* Could implement as one or several extension scripts. Possibly
|
||||
platform-specific.
|
||||
* Concrete example: https://github.com/fadden/6502bench/issues/119
|
||||
* Use a non-JSON format for project files. A custom format would be more
|
||||
compact, easier to hand-edit, and yield better diffs.
|
||||
* Improve "recent files"
|
||||
|
|
Loading…
Reference in New Issue
Block a user