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
A thought would be if that function was made native on the supported platforms and could be enabled in the build to visualise the memory usage... (it's presumably exponentially difficult if it would also support a project or even a single source with multiple files with binary imports and patches, but that would also be part of the wishlist from me; visualising import of file xyz.prg between 0800 to cfff, with patches on locations x,y and z in addition to the plain list of what the pure source file generated as output from its assembly of opcodes).
The text was updated successfully, but these errors were encountered:
Thanks @BacchusFLT!
Exactly this has been in my mind for quite some time, but I did not get the chance to try it out and fix it...yet. Hopefully I will, especially now when I know that someone else would also benefit from it.
I guess this is your own tool:
https://kickassmemoryview.insoft.se/
A thought would be if that function was made native on the supported platforms and could be enabled in the build to visualise the memory usage... (it's presumably exponentially difficult if it would also support a project or even a single source with multiple files with binary imports and patches, but that would also be part of the wishlist from me; visualising import of file xyz.prg between 0800 to cfff, with patches on locations x,y and z in addition to the plain list of what the pure source file generated as output from its assembly of opcodes).
The text was updated successfully, but these errors were encountered: