While we are on the subject of Terminal Window ... Baud Rate ... defaults back to 9600 every time, how about leaving it at whatever set last. or if for some reason you can't, default it to 115200 baud, which 99% of us are using 98% of the time! It is one less thing to have to do to set up the terminal window.
cheers ... BBR
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
cheers ... brian riley, n1bq, underhill center, vermont
The Shoppe at Wulfden www.wulfden.org/TheShoppe/
Brian Riley said...
While we are on the subject of Terminal Window ... Baud Rate ... defaults back to 9600 every time, how about leaving it at whatever set last. or if for some reason you can't, default it to 115200 baud, which 99% of us are using 98% of the time! It is one less thing to have to do to set up the terminal window.
That one has had me puzzled for a while (but obviously not puzzled enough to fix it). The terminal is *supposed* to default to 38400, and it is *supposed* to save your last used settings and restore them. I do have a known bug on Linux & OSX whereby if you open and close bst without opening the terminal at least once, it will blow away your terminal preferences and revert to defaults.
I've bitten the bullet and resurrected my terminal re-work, so hopefully I can knock all these issues on the head sooner rather than later.
@Saphiea, by default, the bst terminal treats any LF / CR / CR/LF / LF/CR sequence as a simple return/newline. I'll make sure there is an option to switch that off for those that actually use CR & LF independently, but as it is in the terminal now it should treat any or all of those as the same.
I've thought about some configurable control codes, the same way I've thought about user-definable key sequences in the main IDE, but both of those require quite some effort to implement and I've just not got around to either of them yet.
File transfers are something I could look at also (I briefly looked into X-Modem a while back) but I never really got very far with it. What formats are people actually using?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.
BradC said...
That one has had me puzzled for a while (but obviously not puzzled enough to fix it). The terminal is *supposed* to default to 38400, and it is *supposed* to save your last used settings and restore them. I do have a known bug on Linux & OSX whereby if you open and close bst without opening the terminal at least once, it will blow away your terminal preferences and revert to defaults.
Yup, sure enough. It saves last setting, but just once bring up/shut down BST w/o accessing Serial Terminal and its bye-bye 115200 and hello 9600!
sigh!!!!!!
cheers ... BBR
p.s. Brad, when will we see 20 Pre1 and PB 85 ????
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
cheers ... brian riley, n1bq, underhill center, vermont
The Shoppe at Wulfden www.wulfden.org/TheShoppe/
BradC: Wow, I have never seen the terminal baud problem under Vista and I would do what you say sometimes (not opening a terminal window).
Terminal section....
If you play with the terminal section, I would like at least an option to try and connect to the same default port·as the main IDE. In other words, not have to do select port and then connect.
I am not after a full-blown terminal program. There are many that do this. Just a minimal version for simple testing would be nice and just a little better that we have now. Here are some further thoughts...
Your cr, lf, cr+lf all translating to cr is fine for most things and should be OK.
An option to select a character for clear screen ($00 NULL and $18 CAN seem to be most common excepting VT100 escape sequences) including and option to·use this sequence·"<cr>--cls--<cr>". This means we could keep the existing log and see where clear screen was done. Very handy to see where something goes wrong before the screen gets cleared and losing what went before. The only reason to actually clear the screen is to delete it from the buffer. Since we can do this manually, it would be fine to always just do the "<cr>--cls--<cr>" sequence.
I have just implemented the following codes in my 1-pin TV driver code as a minimal approach to the terminal handling. Due to space, I cannot fit VT100 mode. However, I think this will surfice for most things people do. It is not a substitute for the full VT100 though.
$00 <null> and $18 <can> does clear screen
$08 backspace
$0A <lf> and $0D <cr>. In my case, <lf> moves down a line (scrolls if required) and stays in the same column
$0B <vt> does home
$1B <esc> is ignored
$1C <fs> right, $1D <gs> left, $1E <rs> up, $1F <us> down. They just move the cursor. Left & right stay on the same row when wrapping and up & down stay in the same column when wrapping without scrolling. This is what I do, but the right/left/up/down is the ASCII preferred sequences (not VT100)
A cursor would be nice (do you have this?? - the testing I have been doing tries to do a cursor so I am unsure)
File Transfer... the simple mechanism that mpark has done in Sphinx is quite·easy to implement. I don't think we need an Xmodem version as we could use a Terminal program for this. Michael's mechanism is also easy for anyone to implement in spin/pasm or on the PC, so it has other benefits here. I do not see any checksum here, but I was sure the PC code implemented a simple bit accumulation although an xor would probably be better. If you are open to this idea I can discuss further. I think we just want something simple with a minimal checksum calculation, and something anyone can implement in their own code. After all, the download is simple and we are using the same connection for that.
'GET & PUT in Sphinx (PUT not implemented)
'-----------------------------------------------
elseif strcomp( @cmdLine, string("GET") )
p += strsize(p) + 1
n := strsize(p)
if n
q := p
if byte[noparse][[/noparse]q] == "*"
q += strsize(q) + 1
' if f.open( q,"W") <> 0 or strsize(p)==0
' abort string(" - can't open")
term.out(0)
term.str(p) 'send filename
term.str(string(5,$82)) 'initiate download
term.out(n)
term.out("f")
repeat 1000
if b := kb.peek
quit
waitcnt(clkfreq>>9+cnt)
ifnot b
abort string(" - File not found")
'-----------------------------------------------
len := kb.in 'PropTerm sends first the FileLength (4 bytes)
b := kb.in
len |= b<<8
b := kb.in
len |= b<<16
b := kb.in
len |= b<<24
n := 0 'counter for received bytes
repeat while n < len
term.out(".") 'trigger next 16 bytes
repeat i from 0 to 15 'receive 16 bytes
if n+i => len 'quit if length reached
quit
b := kb.in
buffer[noparse][[/noparse]i] := b 'store in buffer
f.write(@buffer,16) 'write the buffer to the SD card
n += 16
f.close
'-----------------------------------------------
term.out(13)
term.dec( n )
abort string(" bytes received", 13)
'-----------------------------------------------
'-----------------------------------------------
elseif strcomp( @cmdLine, string("PUT") )
p += strsize(p) + 1
abort string(" not yet implemented", 13)
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Links to other interesting threads:
BradC "Well, a symbol has an alignment. It is the symbol that has the alignment. File " xxx " just imports bytes wherever you put it, so if you have a long symbol then a FILE command it will just squirt that data straight into the DAT section, but if you reference the symbol from spin it will be referenced as a long symbol."
Actually I contend that as symbol has a "type" as shown by the following code:
DAT org 0
byte 'Force zpu_memory to have type BYTE
zpu_memory file "test.bin"
padding byte 0[noparse][[/noparse](zpu_memory_size) - (@padding - @zpu_memory)]
zpu_memory_end
fit (zpu_memory_size / 4)
Now if I access the bytes of test.bin using zpu_memory[noparse][[/noparse] i ] then I will correctly get the bytes indexed by i.
If I now change that first "byte" to "long" then zpu_memory[noparse][[/noparse] i ] will access every LONG in the file correctly.
This implies to me that zpu_memory effectively has a "type" such that the compiler knows to multiply the index i by 1, 2 or 4 in order to step through BYTEs, WORDs or LONGs in the array.
Simply aligning zpu_memory on 1, 2 or 4 byte boundaries would not do that.
Anyway no matter, the only slight "gotcha" here is that you can't specify BYTE, WORD, LONG in the file statement and the alignment (type) is taken from whatever came immediately before. For the unwary that means "zpu_memory[noparse][[/noparse] i ]" can randomly change its behaviour as you change seemingly unrelated code.
Better to write it like this:
zpu_memory byte 'Force zpu_memory to have type BYTE
file "test.bin"
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
For me, the past is not over yet.
I have a small request to make BST a bit more OSX friendly (I know that it is the kind of request that possibly breaks everything!): The preference panels could be in the bst menu under Preferences like the other OSX apps (and thus unify them).
Actually I contend that as symbol has a "type" as shown by the following code:
Of course you are right, and despite the fact it's not what I said, it's what I meant.
The alignment sets the type of the symbol as far as the compiler is concerned.
@Ale, I'd love to do that if only I could figure out how. The Carbon interface I use to build the OSX version just won't seem to allow me access to that menu, or else I'd have both Preferences and About under there. I'll keep looking though.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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 decided to test out your new bst/probBASIC, for windows, everything worked as advertised. I used my modified sircs program as the basis, it ran as expected in bst/propBasic. I then took the compiled SPIN version that bst/propBasic produced, and ran that under bst/SPIN, that also ran as expected. I do not have a linux box setup, so I could not test that. Everything seems to be working as expected.
Bean had mentioned that sometime in the future he will be implementing LMM, how will that work under bst? Have you ever considered adding LMM to bst/Spin?
I just installed Lazarus and saw that they also do not have a preferences item in the Lazarus menu... so I'll not nag again , unless I find a way (do not hold your breath as it was a long ago that I programmed in Pascal, >10 y.).
I just installed Lazarus and saw that they also do not have a preferences item in the Lazarus menu... so I'll not nag again , unless I find a way (do not hold your breath as it was a long ago that I programmed in Pascal, >10 y.).
Well, you wouldn't read about it in a book, but about 10 minutes after I responded to your last post I figured out how to do it! There are a couple of little quirks, but when the next release comes out I hope you like it a bit better [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.
Rsadeika said...
I decided to test out your new bst/probBASIC, for windows, everything worked as advertised. I used my modified sircs program as the basis, it ran as expected in bst/propBasic. I then took the compiled SPIN version that bst/propBasic produced, and ran that under bst/SPIN, that also ran as expected. I do not have a linux box setup, so I could not test that. Everything seems to be working as expected.
Thanks for the feedback. We've all worked pretty hard to make it as smooth as possible on all three platforms.
Rsadeika said...
Bean had mentioned that sometime in the future he will be implementing LMM, how will that work under bst? Have you ever considered adding LMM to bst/Spin?
The LMM implementation is actually in the PropBASIC compiler, so there are no changes to bst required in making it work. Remember, it's LMM not XMM, so it will work with the internal RAM on the propeller, not the numerous external ram solutions around.
I've toyed with a spin to LMM compiler, but just never found the motivation to actually do anything other than toy around with it. Spin / PASM does what I need.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.
Mac user feedback required.
I'm implementing the whole "Top File" thing. On Windows/Linux it's F8-F11 for the standard file compiles, and ctrl-F8->Ctrl-F11 for the top file compiles.
What do I do on the Mac? The reason the key binding is as it is now (Cmd-F8->Cmd->F11) is the Macbook I was originally developing on had OS functions mapped to the native function keys and I could not override it.
Now I need to re-work the key bindings, what are people using and what would be possible to work on the broadest range of Macs ?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.
Changes :
Win32 users can turn off cleartype rendering by disabling "Anti aliased" in the IDE preferences. Ray, does this make the text clearer for you again?
Mac users get the correct application menu and shortcut for preferences. (Tested on PPC 10.4.11 - feedback appreciated on other versions)
Terminal to front if connected after a compile. (Needs heavier testing on Win32/OSX)
Should not blow up if PropBASIC crashed under it and should tell you nicely the compiler died.
Issues :
Mac/Linux users still lose terminal preferences after a bst open/close with no terminal activation.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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 a bit funny about my signature. I'm not much into advertising, and it kinda feels that way.
See, the signature is there forever. Each post gets its own copy of the signature and by putting stuff in there I run the risk of it going out of date. The homepage link (like the avatar picture) is always up to date.
What I've done instead is activated my home page link (second from the left under my Avatar).
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.
BradC: The terminal popup works great. Thanks heaps for this. A great timesaver (well frustration anyway)
re signature - fair enough. I added mine after I was asked and it works great for me to find links to other stuff thet I use regularly. In fact, I often just find an old posting as I know the link is there. Anyway, the homepage link on the avatar is great, which reminds me to change my homepage link - I moved the prop to its own area.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Links to other interesting threads:
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Nothing is impossible, there are only different degrees of difficulty. For every stupid question there is at least one intelligent answer. Don't guess - ask instead. If you don't ask you won't know. If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Thanks for that Sapieha. I'll be completely honest and say I made _no_ changes that might even impact that fault. I honestly have no idea why it was a problem and I made no effort to fix it in this release (although I am attempting to get a Swedish localized copy of XP so I can test stuff like this in the future).
I will continue to try and get a localized copy of XP I can run in a VM for testing though. I figure it'll come in handy for odd things. I'd like to get unicode in file names and object names working properly and I know I can't do that unless I can properly test it.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.
Why I not see In "Open Recent" files that are .pbasic only Spin files are listed ?
Regards
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Nothing is impossible, there are only different degrees of difficulty. For every stupid question there is at least one intelligent answer. Don't guess - ask instead. If you don't ask you won't know. If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Is bst missing a print the file command, or am I just not looking in the correct pull down menu? I thought it would be in the 'File' or 'Edit' pull down, but I cannot find it.
Rsadeika said...
Is bst missing a print the file command, or am I just not looking in the correct pull down menu? I thought it would be in the 'File' or 'Edit' pull down, but I cannot find it.
It's not there. bst does not print.
It's on the todo list but it's a fair way down.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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 am using bst/windows, and their seems to be a problem with the port selection refresh. If I start bst with the protoboard plugged in, lets say com3, and run a program, it finds the port, everything is OK. While still having bst live, I unplug the USB cable for the protoboard, and plug in the demo board USB, lets say com4, and try to do compile and load, it seems to be locked in for com3, and will not let me make the com4 as default. So, what has to be done is, quit bst, start it back up again, and go from scratch. If I have both of them plugged in, then you have to guess as to which one is which. I do not know if this is a bug, or that is the way you designed it. I hope you can make sense of this.
Rsadeika said...
I am using bst/windows, and their seems to be a problem with the port selection refresh. If I start bst with the protoboard plugged in, lets say com3, and run a program, it finds the port, everything is OK. While still having bst live, I unplug the USB cable for the protoboard, and plug in the demo board USB, lets say com4, and try to do compile and load, it seems to be locked in for com3, and will not let me make the com4 as default. So, what has to be done is, quit bst, start it back up again, and go from scratch. If I have both of them plugged in, then you have to guess as to which one is which. I do not know if this is a bug, or that is the way you designed it. I hope you can make sense of this.
It's a bug. I found this 2 days ago when I was experimenting with an XP machine. The current workaround is to go to the IDE Preferences and configure the port manually. I don't know why it does it, and I don't know why it only does it on Windows, but I'll get it sorted.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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
cheers ... BBR
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
cheers ... brian riley, n1bq, underhill center, vermont
The Shoppe at Wulfden
www.wulfden.org/TheShoppe/
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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
That one has had me puzzled for a while (but obviously not puzzled enough to fix it). The terminal is *supposed* to default to 38400, and it is *supposed* to save your last used settings and restore them. I do have a known bug on Linux & OSX whereby if you open and close bst without opening the terminal at least once, it will blow away your terminal preferences and revert to defaults.
I've bitten the bullet and resurrected my terminal re-work, so hopefully I can knock all these issues on the head sooner rather than later.
@Saphiea, by default, the bst terminal treats any LF / CR / CR/LF / LF/CR sequence as a simple return/newline. I'll make sure there is an option to switch that off for those that actually use CR & LF independently, but as it is in the terminal now it should treat any or all of those as the same.
I've thought about some configurable control codes, the same way I've thought about user-definable key sequences in the main IDE, but both of those require quite some effort to implement and I've just not got around to either of them yet.
File transfers are something I could look at also (I briefly looked into X-Modem a while back) but I never really got very far with it. What formats are people actually using?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.
Yup, sure enough. It saves last setting, but just once bring up/shut down BST w/o accessing Serial Terminal and its bye-bye 115200 and hello 9600!
sigh!!!!!!
cheers ... BBR
p.s. Brad, when will we see 20 Pre1 and PB 85 ????
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
cheers ... brian riley, n1bq, underhill center, vermont
The Shoppe at Wulfden
www.wulfden.org/TheShoppe/
Terminal section....
'GET & PUT in Sphinx (PUT not implemented) '----------------------------------------------- elseif strcomp( @cmdLine, string("GET") ) p += strsize(p) + 1 n := strsize(p) if n q := p if byte[noparse][[/noparse]q] == "*" q += strsize(q) + 1 ' if f.open( q,"W") <> 0 or strsize(p)==0 ' abort string(" - can't open") term.out(0) term.str(p) 'send filename term.str(string(5,$82)) 'initiate download term.out(n) term.out("f") repeat 1000 if b := kb.peek quit waitcnt(clkfreq>>9+cnt) ifnot b abort string(" - File not found") '----------------------------------------------- len := kb.in 'PropTerm sends first the FileLength (4 bytes) b := kb.in len |= b<<8 b := kb.in len |= b<<16 b := kb.in len |= b<<24 n := 0 'counter for received bytes repeat while n < len term.out(".") 'trigger next 16 bytes repeat i from 0 to 15 'receive 16 bytes if n+i => len 'quit if length reached quit b := kb.in buffer[noparse][[/noparse]i] := b 'store in buffer f.write(@buffer,16) 'write the buffer to the SD card n += 16 f.close '----------------------------------------------- term.out(13) term.dec( n ) abort string(" bytes received", 13) '----------------------------------------------- '----------------------------------------------- elseif strcomp( @cmdLine, string("PUT") ) p += strsize(p) + 1 abort string(" not yet implemented", 13)▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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
When I have a couple of extra niggly bugs nailed. (Like the terminal settings on OSX/Linux)
On the 21st of Feb.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.
Actually I contend that as symbol has a "type" as shown by the following code:
DAT org 0 byte 'Force zpu_memory to have type BYTE zpu_memory file "test.bin" padding byte 0[noparse][[/noparse](zpu_memory_size) - (@padding - @zpu_memory)] zpu_memory_end fit (zpu_memory_size / 4)Now if I access the bytes of test.bin using zpu_memory[noparse][[/noparse] i ] then I will correctly get the bytes indexed by i.
If I now change that first "byte" to "long" then zpu_memory[noparse][[/noparse] i ] will access every LONG in the file correctly.
This implies to me that zpu_memory effectively has a "type" such that the compiler knows to multiply the index i by 1, 2 or 4 in order to step through BYTEs, WORDs or LONGs in the array.
Simply aligning zpu_memory on 1, 2 or 4 byte boundaries would not do that.
Anyway no matter, the only slight "gotcha" here is that you can't specify BYTE, WORD, LONG in the file statement and the alignment (type) is taken from whatever came immediately before. For the unwary that means "zpu_memory[noparse][[/noparse] i ]" can randomly change its behaviour as you change seemingly unrelated code.
Better to write it like this:
zpu_memory byte 'Force zpu_memory to have type BYTE file "test.bin"▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
For me, the past is not over yet.
Post Edited (heater) : 2/23/2010 9:04:07 AM GMT
I have a small request to make BST a bit more OSX friendly (I know that it is the kind of request that possibly breaks everything!): The preference panels could be in the bst menu under Preferences like the other OSX apps (and thus unify them).
Thanks again !
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Visit some of my articles at Propeller Wiki:
MATH on the propeller propeller.wikispaces.com/MATH
pPropQL: propeller.wikispaces.com/pPropQL
pPropQL020: propeller.wikispaces.com/pPropQL020
OMU for the pPropQL/020 propeller.wikispaces.com/OMU
pPropellerSim - A propeller simulator for ASM development sourceforge.net/projects/ppropellersim
Of course you are right, and despite the fact it's not what I said, it's what I meant.
The alignment sets the type of the symbol as far as the compiler is concerned.
@Ale, I'd love to do that if only I could figure out how. The Carbon interface I use to build the OSX version just won't seem to allow me access to that menu, or else I'd have both Preferences and About under there. I'll keep looking though.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.
Bean had mentioned that sometime in the future he will be implementing LMM, how will that work under bst? Have you ever considered adding LMM to bst/Spin?
Ray
I just installed Lazarus and saw that they also do not have a preferences item in the Lazarus menu... so I'll not nag again
Thanks anyways!
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Visit some of my articles at Propeller Wiki:
MATH on the propeller propeller.wikispaces.com/MATH
pPropQL: propeller.wikispaces.com/pPropQL
pPropQL020: propeller.wikispaces.com/pPropQL020
OMU for the pPropQL/020 propeller.wikispaces.com/OMU
pPropellerSim - A propeller simulator for ASM development sourceforge.net/projects/ppropellersim
Well, you wouldn't read about it in a book, but about 10 minutes after I responded to your last post I figured out how to do it! There are a couple of little quirks, but when the next release comes out I hope you like it a bit better [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.
Thanks for the feedback. We've all worked pretty hard to make it as smooth as possible on all three platforms.
The LMM implementation is actually in the PropBASIC compiler, so there are no changes to bst required in making it work. Remember, it's LMM not XMM, so it will work with the internal RAM on the propeller, not the numerous external ram solutions around.
I've toyed with a spin to LMM compiler, but just never found the motivation to actually do anything other than toy around with it. Spin / PASM does what I need.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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 implementing the whole "Top File" thing. On Windows/Linux it's F8-F11 for the standard file compiles, and ctrl-F8->Ctrl-F11 for the top file compiles.
What do I do on the Mac? The reason the key binding is as it is now (Cmd-F8->Cmd->F11) is the Macbook I was originally developing on had OS functions mapped to the native function keys and I could not override it.
Now I need to re-work the key bindings, what are people using and what would be possible to work on the broadest range of Macs ?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.
Changes :
Win32 users can turn off cleartype rendering by disabling "Anti aliased" in the IDE preferences. Ray, does this make the text clearer for you again?
Mac users get the correct application menu and shortcut for preferences. (Tested on PPC 10.4.11 - feedback appreciated on other versions)
Terminal to front if connected after a compile. (Needs heavier testing on Win32/OSX)
Should not blow up if PropBASIC crashed under it and should tell you nicely the compiler died.
Issues :
Mac/Linux users still lose terminal preferences after a bst open/close with no terminal activation.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.
Update: Yes the fonts are back to crisp, thanks. (Note you defaulted this way)
I will switch laptops and try the auto terminal focus.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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
Post Edited (Cluso99) : 2/24/2010 6:25:08 AM GMT
See, the signature is there forever. Each post gets its own copy of the signature and by putting stuff in there I run the risk of it going out of date. The homepage link (like the avatar picture) is always up to date.
What I've done instead is activated my home page link (second from the left under my Avatar).
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.
re signature - fair enough. I added mine after I was asked and it works great for me to find links to other stuff thet I use regularly. In fact, I often just find an old posting as I know the link is there. Anyway, the homepage link on the avatar is great, which reminds me to change my homepage link - I moved the prop to its own area.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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
Now ABOUT function correctly for me
Regards
Christoffer J
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Nothing is impossible, there are only different degrees of difficulty.
For every stupid question there is at least one intelligent answer.
Don't guess - ask instead.
If you don't ask you won't know.
If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Sapieha
Thanks for that Sapieha. I'll be completely honest and say I made _no_ changes that might even impact that fault. I honestly have no idea why it was a problem and I made no effort to fix it in this release (although I am attempting to get a Swedish localized copy of XP so I can test stuff like this in the future).
I will continue to try and get a localized copy of XP I can run in a VM for testing though. I figure it'll come in handy for odd things. I'd like to get unicode in file names and object names working properly and I know I can't do that unless I can properly test it.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.
Huh??? Where???
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
cheers ... brian riley, n1bq, underhill center, vermont
The Shoppe at Wulfden
www.wulfden.org/TheShoppe/
I'ts on Bean's top post:
http://forums.parallax.com/showthread.php?p=867134
Jim
Why I not see In "Open Recent" files that are .pbasic only Spin files are listed ?
Regards
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Nothing is impossible, there are only different degrees of difficulty.
For every stupid question there is at least one intelligent answer.
Don't guess - ask instead.
If you don't ask you won't know.
If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Sapieha
I meant the PropBasic-bst version of 85!
Oh ho, I see ... they changed the directory name from what we field testers were using. Got it now.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
cheers ... brian riley, n1bq, underhill center, vermont
The Shoppe at Wulfden
www.wulfden.org/TheShoppe/
Post Edited (Brian Riley) : 2/24/2010 8:13:24 PM GMT
Oh, I missed that one. Thanks [noparse]:)[/noparse] I'll fix that in the next release.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.
Ray
It's not there. bst does not print.
It's on the todo list but it's a fair way down.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.
Ray
It's a bug. I found this 2 days ago when I was experimenting with an XP machine. The current workaround is to go to the IDE Preferences and configure the port manually. I don't know why it does it, and I don't know why it only does it on Windows, but I'll get it sorted.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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.