heater said...
Missing OBJ and COG addresses in status bar for sub objects.
If I hit F8 in my top object and it compiles without error then I can click on labels in the file and see their addresses in the status bar. OK.
If I now select a TAB of a sub object clicking labels there gives nothing in the status bar.
Returning to the main object TAB I find there is no status bar info available any more.
Correct. That is how it's designed to work. I never got around to expanding into sub-objects, and the easiest way of coping with multiple tabs was to do it the way I did it.
It's on the list of things to do, but I've not quite made it there yet.
While I'm here. 0.19.3 is up with a fix for your crash bug. Thanks [noparse]:)[/noparse]
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
Wow, BradC, you must be the most persistent and fastest bug fixer in the history of computing.
I'm with you on the status info issue. I guess it only bugs me as I can't just hit F8 on a sub object to instantly regenerate the info. The sub object does not compile without some #defines.
I know, I know, put the defines in the project...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
For me, the past is not over yet.
heater said...
Wow, BradC, you must be the most persistent and fastest bug fixer in the history of computing.
Crash bugs rate very high on my radar (and I happen to be at home, in front of the machine and have 10 seconds to pause, breathe and fix - does not happen often these days)
heater said...
I'm with you on the status info issue. I guess it only bugs me as I can't just hit F8 on a sub object to instantly regenerate the info. The sub object does not compile without some #defines.
I think I'll have a solution that will work in the next week or so, but I need to think about it a bit harder. It's something I'd find useful also, but I never got around to doing anything about it properly. I'd also like to be able to right click on a sub-object variable and just open that object in a new tab.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
I'm with you on the status info issue. I guess it only bugs me as I can't just hit F8 on a sub object to instantly regenerate the info. The sub object does not compile without some #defines.
Try 0.19.4-Pre1 and see if it does what you expect with the symbols in other tabs and sub-objects. It's very ropey, experimental code but I've not managed to blow it up here and it seems to do what I want it to do.
Oh, and right-click to open the object under the cursor should work too (click on the objects symbol, not the objects name).
Again, all this only works after a successful compile.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
Brad,
If it's not too much trouble, could you make it that when you use "Compile Basic to Spin" that it brings the .spin file forward ?
I can't tell you how many times I used the command over because I thought it didn't do anything.
Bean
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Use BASIC on the Propeller with the speed of assembly language.
Bean said...
Brad,
If it's not too much trouble, could you make it that when you use "Compile Basic to Spin" that it brings the .spin file forward ?
I can't tell you how many times I used the command over because I thought it didn't do anything.
Any chance of having the rather useful terminal just pass-through all the control keys? At present I have yet to find a terminal emulator as good as the windows TeraTerm to run on Linux, it is so frustrating. If I want to send some special control combinations to a serial device but it is very awkward. Also, is there a way to send characters > $7f from the terminal in Linux?
TeraTerm does run under Wine but woefully so.
BTW, this thread is so huge that we can't find any sub-threads. Maybe it might be good for us to start new threads that are more specific?
Any chance of having the rather useful terminal just pass-through all the control keys?
I can't see why not. I'll have a play and see what I can come up with.
I'm about half way through a terminal re-write at the moment. The new code allows for different emulation / display modes (at the moment it does raw ascii / hex / PST compatible and VT100 compatible. It would be easy enough to add a pass-through mode for control-characters. It's progressing slower than I'd like however.
Peter Jakacki said...
Also, is there a way to send characters > $7f from the terminal in Linux?
TeraTerm does run under Wine but woefully so.
How do you enter them?
As for sub-threads.. Personally I find a single thread easier to keep up with, but feel free to start other threads if you feel it would help.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
Perhaps having a single radio button which forces the msb high would be a useful way of sending characters > $7F. It certainly would keep it simple and universal across platforms. Alternatively a simple HEX SEND box where the code can be entered directly would also work.
Hey Ray, have you never typed CTRL+SHIFT+@ to send a null? Same goes for every other control character right up to CTRL+_ for $1F. Just like machine code, you get to know the codes like the back of your hand.
But yes, a HEX box would be most suitable (as well).
Brad, there is also the way the terminal handles control codes that it receives as it presently prints a "?" for any it does not handle. Personally I like to see the code received like it does in GtkTerm where it cleverly renders two hex digits in a single character. Although this would be nice I would be happy to see the received characters display as hex in a separate multi-line box (along with the normal text box) as this is quite easy to achieve and makes it very clear what is actually being received character by character. Actually, if you do that along with the hex transmit box it will be a really useful terminal, even if it isn't VT100 compatible.
Peter Jakacki said...
Brad, there is also the way the terminal handles control codes that it receives as it presently prints a "?" for any it does not handle. Personally I like to see the code received like it does in GtkTerm where it cleverly renders two hex digits in a single character. Although this would be nice I would be happy to see the received characters display as hex in a separate multi-line box (along with the normal text box) as this is quite easy to achieve and makes it very clear what is actually being received character by character. Actually, if you do that along with the hex transmit box it will be a really useful terminal, even if it isn't VT100 compatible.
It's not GtkTerm that does that specifically. It's a feature of the GTK font rendering and therefore not available on Windows or OSX.
I have an idea for a separate floating form for hex input/output where you can send / display hex simultaneously with the main terminal.
I've got some time put aside to work on the terminal a bit today, let me see what I can come up with.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
Peter: Thanks for the hint - all these years with PC's and I never knew that. Yes, I used to be able to totally recite the ASCII table. I am a little rusty on some of the control codes, but the rest is permantly burnt in
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Links to other interesting threads:
The serial terminal has a hex window (in the File Menu). Also Copy / Paste now work from the Edit menu in the terminal (hot keys don't as we are working towards passing control codes through). Try it out and see if you can break it.
The hex window works in parallel with the normal terminal window. You can only display / send hex from that window, so when you enter stuff in the command box to send it must be standard hex numbers "01 02 03 DF" and so on. There is a history of the last entered commands so you can point and shoot from previous entries. You can either use the send button or Enter key to send the string.
The hex display history is limited to 15 lines at the moment due to some hitches with the display components. If you need more than that then you can use the hex display option in the main terminal I guess.
I've given it a light torturing under linux and a boot and echo test under Wine (win32 build).
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
That looks good Brad with one little touch-up to the hex display's font just to make sure the hex bytes line up. So it's not really necessary to pass through all the control keys now and I like the way the hex send just allows you to keep hitting the enter to repeat the last sequence (unintended feature?).
Preferably we would have the same font for both windows and I favor ones that display unambiguous zeros as does the Parallax font. Any chance of using that?
Peter Jakacki said...
That looks good Brad with one little touch-up to the hex display's font just to make sure the hex bytes line up. So it's not really necessary to pass through all the control keys now and I like the way the hex send just allows you to keep hitting the enter to repeat the last sequence (unintended feature?).
Nope, fully intended. I thought it would work well with the scrollback buffer of previously sent commands. I guess I should put a limit on the size of that buffer and think about perhaps saving it in the config file for persistent command history.
Peter Jakacki said...
Preferably we would have the same font for both windows and I favor ones that display unambiguous zeros as does the Parallax font. Any chance of using that?
Done. The font is now set to the same font the terminal uses, so you can pick your font manually if you like. Defaults to Parallax.
0.19.4-Pre6 up.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
Wonderful, this will keep me happy until tomorrow
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
Still happy, thanks a lot Brad!
I started using your nice software, I like it much.
But, sorry for my ignorance; when I use therminal, I am unable to send some control character as CtrlX ($18) or CtrlV ($16) to my application on Propeller. What am I doing wrong?
With PST, I have never had problems in using such control characters.
dossic said...
I started using your nice software, I like it much.
But, sorry for my ignorance; when I use therminal, I am unable to send some control character as CtrlX ($18) or CtrlV ($16) to my application on Propeller. What am I doing wrong?
With PST, I have never had problems in using such control characters.
Thanks so much
Carlo
Currently the terminal program traps most control characters and prevents them being sent through. It is being rectified, but at the moment it's still an issue.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
I'm looking forward to receiving the new release! I need to send those character in my project - a new electrochemical instrument; ^X stops scanning, ^V and ^T set current range.
dossic said...
I'm looking forward to receiving the new release! I need to send those character in my project - a new electrochemical instrument; ^X stops scanning, ^V and ^T set current range.
Thanks so much for the hyperfast answer....
No problem. I should have it fixed by the end of the weekend if things go according to plan.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
Comments
If I hit F8 in my top object and it compiles without error then I can click on labels in the file and see their addresses in the status bar. OK.
If I now select a TAB of a sub object clicking labels there gives nothing in the status bar.
Returning to the main object TAB I find there is no status bar info available any more.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
For me, the past is not over yet.
Correct. That is how it's designed to work. I never got around to expanding into sub-objects, and the easiest way of coping with multiple tabs was to do it the way I did it.
It's on the list of things to do, but I've not quite made it there yet.
While I'm here. 0.19.3 is up with a fix for your crash bug. Thanks [noparse]:)[/noparse]
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
I'm with you on the status info issue. I guess it only bugs me as I can't just hit F8 on a sub object to instantly regenerate the info. The sub object does not compile without some #defines.
I know, I know, put the defines in the project...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
For me, the past is not over yet.
Crash bugs rate very high on my radar (and I happen to be at home, in front of the machine and have 10 seconds to pause, breathe and fix - does not happen often these days)
I think I'll have a solution that will work in the next week or so, but I need to think about it a bit harder. It's something I'd find useful also, but I never got around to doing anything about it properly. I'd also like to be able to right click on a sub-object variable and just open that object in a new tab.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
Try 0.19.4-Pre1 and see if it does what you expect with the symbols in other tabs and sub-objects. It's very ropey, experimental code but I've not managed to blow it up here and it seems to do what I want it to do.
Oh, and right-click to open the object under the cursor should work too (click on the objects symbol, not the objects name).
Again, all this only works after a successful compile.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
Compile some moderately complex code. Click on an object symbol and press ctrl-space.
Again.. very preliminary code..
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
For me, the past is not over yet.
If it's not too much trouble, could you make it that when you use "Compile Basic to Spin" that it brings the .spin file forward ?
I can't tell you how many times I used the command over because I thought it didn't do anything.
Bean
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Use BASIC on the Propeller with the speed of assembly language.
PropBASIC thread http://forums.parallax.com/showthread.php?p=867134
March 2010 Nuts and Volts article·http://www.parallax.com/Portals/0/Downloads/docs/cols/nv/prop/col/nvp5.pdf
·
Done. Look for 0.19.4-Pre3 in www.fnarfbargle.com/bst/snapshots any time in the next 5 minutes
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
Thanks.
Bean
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Use BASIC on the Propeller with the speed of assembly language.
PropBASIC thread http://forums.parallax.com/showthread.php?p=867134
March 2010 Nuts and Volts article·http://www.parallax.com/Portals/0/Downloads/docs/cols/nv/prop/col/nvp5.pdf
·
Off by one error. Ctrl-space object export list was missing first parameter in each method.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
Any chance of having the rather useful terminal just pass-through all the control keys? At present I have yet to find a terminal emulator as good as the windows TeraTerm to run on Linux, it is so frustrating. If I want to send some special control combinations to a serial device but it is very awkward. Also, is there a way to send characters > $7f from the terminal in Linux?
TeraTerm does run under Wine but woefully so.
BTW, this thread is so huge that we can't find any sub-threads. Maybe it might be good for us to start new threads that are more specific?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
*Peter*
I can't see why not. I'll have a play and see what I can come up with.
I'm about half way through a terminal re-write at the moment. The new code allows for different emulation / display modes (at the moment it does raw ascii / hex / PST compatible and VT100 compatible. It would be easy enough to add a pass-through mode for control-characters. It's progressing slower than I'd like however.
How do you enter them?
As for sub-threads.. Personally I find a single thread easier to keep up with, but feel free to start other threads if you feel it would help.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
*Peter*
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Links to other interesting threads:
· Home of the MultiBladeProps: TriBlade,·RamBlade,·SixBlade, website
· Single Board Computer:·3 Propeller ICs·and a·TriBladeProp board (ZiCog Z80 Emulator)
· Prop Tools under Development or Completed (Index)
· Emulators: CPUs Z80 etc; Micros Altair etc;· Terminals·VT100 etc; (Index) ZiCog (Z80) , MoCog (6809)·
· Prop OS: SphinxOS·, PropDos , PropCmd··· Search the Propeller forums·(uses advanced Google search)
My cruising website is: ·www.bluemagic.biz·· MultiBlade Props: www.cluso.bluemagic.biz
But yes, a HEX box would be most suitable (as well).
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
*Peter*
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
*Peter*
It's not GtkTerm that does that specifically. It's a feature of the GTK font rendering and therefore not available on Windows or OSX.
I have an idea for a separate floating form for hex input/output where you can send / display hex simultaneously with the main terminal.
I've got some time put aside to work on the terminal a bit today, let me see what I can come up with.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
*Peter*
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Links to other interesting threads:
· Home of the MultiBladeProps: TriBlade,·RamBlade,·SixBlade, website
· Single Board Computer:·3 Propeller ICs·and a·TriBladeProp board (ZiCog Z80 Emulator)
· Prop Tools under Development or Completed (Index)
· Emulators: CPUs Z80 etc; Micros Altair etc;· Terminals·VT100 etc; (Index) ZiCog (Z80) , MoCog (6809)·
· Prop OS: SphinxOS·, PropDos , PropCmd··· Search the Propeller forums·(uses advanced Google search)
My cruising website is: ·www.bluemagic.biz·· MultiBlade Props: www.cluso.bluemagic.biz
The serial terminal has a hex window (in the File Menu). Also Copy / Paste now work from the Edit menu in the terminal (hot keys don't as we are working towards passing control codes through). Try it out and see if you can break it.
The hex window works in parallel with the normal terminal window. You can only display / send hex from that window, so when you enter stuff in the command box to send it must be standard hex numbers "01 02 03 DF" and so on. There is a history of the last entered commands so you can point and shoot from previous entries. You can either use the send button or Enter key to send the string.
The hex display history is limited to 15 lines at the moment due to some hitches with the display components. If you need more than that then you can use the hex display option in the main terminal I guess.
I've given it a light torturing under linux and a boot and echo test under Wine (win32 build).
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
Preferably we would have the same font for both windows and I favor ones that display unambiguous zeros as does the Parallax font. Any chance of using that?
BTW, just noticed that we now have copy/paste
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
*Peter*
Nope, fully intended. I thought it would work well with the scrollback buffer of previously sent commands. I guess I should put a limit on the size of that buffer and think about perhaps saving it in the config file for persistent command history.
Done. The font is now set to the same font the terminal uses, so you can pick your font manually if you like. Defaults to Parallax.
0.19.4-Pre6 up.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
tick
Still happy, thanks a lot Brad!
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
*Peter*
But, sorry for my ignorance; when I use therminal, I am unable to send some control character as CtrlX ($18) or CtrlV ($16) to my application on Propeller. What am I doing wrong?
With PST, I have never had problems in using such control characters.
Thanks so much
Carlo
Currently the terminal program traps most control characters and prevents them being sent through. It is being rectified, but at the moment it's still an issue.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
Thanks so much for the hyperfast answer....
Yours Carlo
No problem. I should have it fixed by the end of the weekend if things go according to plan.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
This is a new, err, feature. It was OK some time ago.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
For me, the past is not over yet.
That's odd. That was the crash I was supposed to have fixed in -pre3 !
<edit> and worse still, I can't reproduce it. Can you shoot me a file that causes it to crash for you please?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.