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
The idea is based on the Online Script and Template Repositories available through the menu system of the 010 Editor. The repositories contain a list of user and creator made examples that can be adapted to other purposes or used as is. I was thinking call_scm_func would be a good response to requests for custom opcodes from new coders.
Why reinvent the wheel? I've only seen a handful of examples of call_scm_func, and have only written a few myself. I think I'd be more likely to use and write scm functions if they were easier to find or share.
For context, I figured my memory management scripts would be a whole lot easier to write if the read and write memory commands included a parameter of an offset from the initial address. For that matter, even easier if array parameters for index, record size and field offsets were also part of the command. Something like,
Something like this would work well for read and write, but how could this be written as a conditional command? That's a nice bonus to the aDMA strategies I've been using for embedded scripts; the form for reading and writing addresses can be used directly in conditional commands.
The text was updated successfully, but these errors were encountered:
I'd seen a few (not very successful) attempts on making a list of SCM functions. Do you have an idea on how to provide a convenient way for the community to share the functions?
I can help with publishing the repository anywhere including the docs site, here at GitHub, sannybuilder.com and/or cleo.li, or include with Sanny.
The idea is based on the Online Script and Template Repositories available through the menu system of the 010 Editor. The repositories contain a list of user and creator made examples that can be adapted to other purposes or used as is. I was thinking call_scm_func would be a good response to requests for custom opcodes from new coders.
Why reinvent the wheel? I've only seen a handful of examples of call_scm_func, and have only written a few myself. I think I'd be more likely to use and write scm functions if they were easier to find or share.
For context, I figured my memory management scripts would be a whole lot easier to write if the read and write memory commands included a parameter of an offset from the initial address. For that matter, even easier if array parameters for index, record size and field offsets were also part of the command. Something like,
`0AB1: call_scm_func @WriteMemory 0xBA86F0 size 2 value 1 virtual_protect 0 offset 0 array_index 3 record_length 40 field_offset 20'
Something like this would work well for read and write, but how could this be written as a conditional command? That's a nice bonus to the aDMA strategies I've been using for embedded scripts; the form for reading and writing addresses can be used directly in conditional commands.
The text was updated successfully, but these errors were encountered: