@Rayman said:
@macca That looks interesting... The debug terminal thing doesn't work with flexprop, all debug seems to go to same window, so must be some magic to make it work in Spin Tools IDE...
The debug terminal is one of the few debug windows that does work with flexprop, see for example the flexprop/samples/debug/debug_tex.spin2 example. The magic that all of the IDEs use to redirect output is the backtick TERM command. WIthout that everything just goes to the default serial window.
(You have to be using one of the flexprop internal terminal emulators for this to work; the external terminal emulators do their own thing and it's up to them how they handle backtick debug commands, but I have yet to see one that parses them ).
Ok @ersmith guess should try that out.
But don’t really have a problem with either of these gui. It’s just prop tool that doesn’t have an automatic terminal window…
I updated my jm_debug_term object to allow the use of arbitrary colors that are available in Spin Tools 0.48.1. Note that when changing the foreground or background you modify color set 0, though it's not likely that a practical app would mix the use of the default color sets with arbitrary colors.
If we could load the old IBM character font we could have text output like on the early IBM PCs and clones!
Hopefully, @cgracey will add the ability to change the foreground and background colors in PNut. Would also be nice if zstr() worked in the debug terminal window, too.
Comments
My mistake, Marco -- I didn't look closely enough to see that "on" was part of a string, not a command. Sorry.
The debug terminal is one of the few debug windows that does work with flexprop, see for example the flexprop/samples/debug/debug_tex.spin2 example. The magic that all of the IDEs use to redirect output is the backtick TERM command. WIthout that everything just goes to the default serial window.
(You have to be using one of the flexprop internal terminal emulators for this to work; the external terminal emulators do their own thing and it's up to them how they handle backtick debug commands, but I have yet to see one that parses them
).
Ok @ersmith guess should try that out.
But don’t really have a problem with either of these gui. It’s just prop tool that doesn’t have an automatic terminal window…
I tested the new version and all the problems disappeared.
Now I can compile all my projects and run them all.
Thank you macca for your work.
On MacOS I found some GUI issues:
Excellent!
Yes, white on light-gray isn't much readable... I'll try to fix these issue for the next release.
I updated my jm_debug_term object to allow the use of arbitrary colors that are available in Spin Tools 0.48.1. Note that when changing the foreground or background you modify color set 0, though it's not likely that a practical app would mix the use of the default color sets with arbitrary colors.
If we could load the old IBM character font we could have text output like on the early IBM PCs and clones!
Hopefully, @cgracey will add the ability to change the foreground and background colors in PNut. Would also be nice if zstr() worked in the debug terminal window, too.