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
We have quite a few information already (and are able to retrieve some more from some known memory locations) in order to have an idea of the current execution state of a TI-basic program.
With this information, we should be able to make some kind of "debugger", or at least a live-viewer of what's going on:
current program being run (basic_prog)
current line (curPC)
current variables (we have that already with the var list/viewer)
The variable viewer as of now can already show (and reformat, but I guess we can't use that feature here, unless we have original line info...?)
This "TI-Basic" debugger will likely require a new dedicated dock in order to maximize its usefulness and UX, with a custom UI being split in 2 parts:
a code viewer (like the current one, with syntax highlight, line numbers etc.)
highlighting the currently executing line (and fetched parts)
We have quite a few information already (and are able to retrieve some more from some known memory locations) in order to have an idea of the current execution state of a TI-basic program.
With this information, we should be able to make some kind of "debugger", or at least a live-viewer of what's going on:
basic_prog
)curPC
)The variable viewer as of now can already show (and reformat, but I guess we can't use that feature here, unless we have original line info...?)
This "TI-Basic" debugger will likely require a new dedicated dock in order to maximize its usefulness and UX, with a custom UI being split in 2 parts:
I'll add that to the "v2.0 - source-level debugging" release target, as it seems quite appropriate, but I guess we'll see over time how it develops.
The text was updated successfully, but these errors were encountered: