Great, I saw that I can select Serial/USB ports and I guess it's scanning those as well...
Got to try it out later tonight...
The only thing I'm missing so to say is the indentation markers to see what code belongs to which block...
Awesome job...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Living on the planet Earth might be expensive but it includes a free trip around the sun every year...
Experience level:
[noparse][[/noparse] ] Let's connect the motor to pin 1, it's a 6V motor so it should be fine.
[noparse][[/noparse] ] OK, I got my resistors hooked up with the LEDs.
[noparse][[/noparse]X] I got the Motor hooked up with the H-bridge and the 555 is supplying the PWM.
[noparse][[/noparse] ] Now, if I can only program the BOE-BOT to interface with he Flux Capacitor.
[noparse][[/noparse] ] I dream in SX28 assembler...
The only thing I'm missing so to say is the indentation markers to see what code belongs to which block...
That bit is part of the syntax highlighter code, and I've barely sketched out the skeleton yet. Once I get the core reliable and working that is next on the agenda.
It will happen, just not fast I'm sorry to say..
Finally got home and had a chance to work with it[noparse]:)[/noparse]
I should begin by saying that I didn't believe that bst on a Mac was even possible... so imagine my delight!!!!
bst is now scriptable!!!!
Proof:
tell application "bst"
activate
end tell
tell application "System Events"
if UI elements enabled then
tell process "bst.osx"
set frontmost to true
click menu item "Compile and Load EEPROM" of menu 1 of menu bar item "Compile" of menu bar 1
--get every action of menu item "Compile and Load EEPROM" of menu 1 of menu bar item "Compile" of menu bar 1
end tell
end if
end tell
this applescript causes bst to compile and load the eeprom...AND that is good enough for me[noparse]:)[/noparse]
Nothing funky... computer is happy.
Minor issues
bst doesn't find the Prop until I tell it to... remember I'm on a Mac G5 10.4.1.1.1.1.1...... so there could be an issue that you could easily
ignore... it is really a legacy puter[noparse]:)[/noparse]
my terminal program can open bst but the file to be loaded isn't... doesn't matter if it is in the same directory with bst or not.
Since applescript works just fine... I can work around this quite nicely... so please satisfy everyone else first.
haven't had a chance to hook up more than one prop yet... but I'm drooling at the thought.
Pace yourself... I'm really excited about this and I don't want you to burn yourself out.
Rich, if you are scripting it to that extent, would you be better using bstc and doing it from there?
I found out last night that OSX uses some weird Smile drag'n'drop events to load files from the finder rather than command line entries.
If you call bst.osx directly (located inside bst.app) it will open a file from the command line for you. I've added fixing that from Finder to my list though.
In one of your answers you said that the mac screen can act as a serial terminal...
screen /dev/ttySO 9600
This doesn't work for me either... can't find ttySO
but this applescript does work:
tell application "Terminal"
do script with command "screen /dev/tty.usbserial-A1001gJp"
set number of rows of window 1 to 100
set number of columns of window 1 to 80
set background color of window 1 to "black"
set normal text color of window 1 to "green"
set custom title of window 1 to "SerialOut"
end tell
In one of your answers you said that the mac screen can act as a serial terminal...
screen /dev/ttySO 9600
This doesn't work for me either... can't find ttySO
No.. it won't if your serial port is not on /dev/ttyS0.
Based on what you wrote below this, this should work for you.
screen /dev/tty.usbserial-A1001gJp 9600
Glad you found a solution in any case.
As for the bst.osx..
./bst.osx /Users/Brad/test.spin
Opens the file right up here.. *but* a proportion of the time I can't focus the bst window. It displays but won't accept mouse clicks..
Can't say I'm not learning alot about the peculiarities of OSX [noparse];)[/noparse]
What did you mean by this bit?
rjo_ said...
Minor issues
bst doesn't find the Prop until I tell it to... remember I'm on a Mac G5 10.4.1.1.1.1.1...... so there could be an issue that you could easily
ignore... it is really a legacy puter[noparse]:)[/noparse]
if you fire it straight up and click "Detect Propeller" does it not locate the port straight off?
If not, when you open the ports box, what does it locate?
No such thing as a "Legacy Computer" for me, which is why I'm now working on Win95 support. If I can get software to run on it, I want it running as well as it does on any other platform.
I've got a 10.4.11 G4 at home, so I can test on that anyway.
The peculiarities of OSX run deep... that's why: "if something works... don't touch it[noparse]:)[/noparse]"
I only have one problem for which I can't think of a workaround... so things are beautatious[noparse]:)[/noparse]
First to answer your question: When I start bst... I first have to do a "detect Prop" before I can compile ... I don't remember if this is how it was in the prior version of bst or not. It isn't really a problem... more of a "feature."
Also when I use applescript to tell bst to compilem the current window it works fine... but before I can tell it to compile again I have to tell it to 'detect prop" again... again this not a much of a problem.
When I switch from one window to another... I have to do another "detect Prop."
I have a feeling that there is a common source for all of this, but I also have a the fear that if you chase this kind of thing into the rat's nest you'll never come out.
I'm using a bash shell... and for anyone else that reads this thread... as with the serial terminal in XP... you have to exit the terminal to give the port back to bst... in order for bst to be able to see the PROP. To exit out of the serial terminal created by the command line Screen you simply hold the commandkey down and strike the "a" key... followed by a commandkey down with the backslash key {"\")
There is one issue that I don't yet have a workaround for... when I have a plain text document... saved as a spin file... I can load the file into bst and compile... no problem. But if I open the same document in TextEdit and then copy and paste it into bst... I get a compile error.
I can even create the file in textedit... save it and then open it with bst and everything is fine... but the same file copied from textedit and pasted into bst throws a compile error... this is a problem... since my workarounds for the command line issues have to do with controlling textedit and then automatically copying and pasting the results into a bst window for compilation...
I am hoping that you or someone else will know of a way to do this sort of thing without having to modify your code.
By the way... from the number of views that this thread is getting, I would say that you are on a hot topic with bst[noparse]:)[/noparse]
The peculiarities of OSX run deep... that's why: "if something works... don't touch it[noparse]:)[/noparse]"
I only have one problem for which I can't think of a workaround... so things are beautatious[noparse]:)[/noparse]
First to answer your question: When I start bst... I first have to do a "detect Prop" before I can compile ... I don't remember if this is how it was in the prior version of bst or not. It isn't really a problem... more of a "feature."
Ok, what happens if you don't "detect Prop" before you compile? Does it do anything? Give an error message?
Does it do this when you are using it normally with the mouse or only when you script it?
rjo_ said...
There is one issue that I don't yet have a workaround for... when I have a plain text document... saved as a spin file... I can load the file into bst and compile... no problem. But if I open the same document in TextEdit and then copy and paste it into bst... I get a compile error.
What _is_ the compile error?
I just tried it here and the error I got was that it can't locate objects.
This makes perfect sense as when you paste code into the window, it does not know where it has come from on disk, and therefore it has no idea which directory to look in for the objects that might go along with it.
This morning I started out getting some errors.... in a variety of ways. But at the moment, I don't get any errors except when I paste a file into bst that has objects in them... which makes perfect sense.
I also noticed earlier that if I waited after starting up bst... things worked ok... and there seems to be a lag between my keyboard and my screen...
I'm thinking my puter has a problem.
time for a virus scan... where did I put my norton's
Just to be complete... Officially... with your comment about object directories, it appears that I don't have a problem that doesn't have a work around... I will have to play with my appleevents to be sure of this.
Just to be complete... since I'm working on a G5 and this might be peculiar to it.
(I restarted my computer... the keyboard latency is fine. Playing with appleevents can really screw up a computer: )
I manually start bst... open a file containing objects... compile to EEProm... no problem first time... after playing around for a while sometimes it says it can't find prop.
I then open the same file in textEdit and copy all, tjem select all text in my window (containing the manually loaded spin file) and paste...
Then I try to manually compile to eeprom... I get "No Prop Detected on port (name of my port)."...BUT if I just try to compile to eeprom again it works fine. And if start bst and do a "detect Prop" first, there is no problem.
Since I'm working on automation... I can easily to a detect Prop every time... so this is nothing.
If I paste a spin file containing objects into an empty window, I get a compile error... as expected and explained by you.
BUT the good news is that if I paste the same spin file into a window with a spin file (with objects) previously loaded from bst into bst... then the object reference doesn't cause a problem... which is the workaround for this particular issue[noparse]:)[/noparse]
Maybe you could include BST's root as the default object directory?
Maybe you could include BST's root as the default object directory?
Ok, the prop detection issues I'll work on. It's entirely possible there is a timing glitch on powerpc.
I've tested it extensively, but it's entirely possible I'm missing something. The propeller can be quite sensitive about it's various time delays.
As for the issue of bst's root. Is that the directory bst resides in, or the directory you start it from?
If it's the former you can just add it to the compiler search path in the compiler prefs dialog.
If it's the latter, perhaps I can look at how I might do that.
I still wonder if you are automating it to that degree, if you would not be better using bstc.. do you *need* the editor components?
Been using BST for a few days over here and I'm extremely pleased with it under Ubuntu.
Only complaint being that it dies very badly when it tried to compile bad code.
Oldbitcollector said...
Been using BST for a few days over here and I'm extremely pleased with it under Ubuntu.
Only complaint being that it dies very badly when it tried to compile bad code.
Looking forward to your next release!
OBC
Ooo.. can you send me the bad code that kills it? I can't fix it unless I can reproduce it.
I've added a feature or two, so I'm kinda getting ready for another release soonish, but I'd like to be able to fix this crash bug before I do that now.
Did the autosave work for you when it crashed?
if you could send the crash inducing code to brad at fnarfbargle dot com, or post it here I'd be really, really appreciative.
I've had some problem with the programming as well...
All of the sudden it would not find the propeller...
Kept trying to detect the prop a few times and then it start working again...
Weird...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Living on the planet Earth might be expensive but it includes a free trip around the sun every year...
Experience level:
[noparse][[/noparse] ] Let's connect the motor to pin 1, it's a 6V motor so it should be fine.
[noparse][[/noparse] ] OK, I got my resistors hooked up with the LEDs.
[noparse][[/noparse]X] I got the Motor hooked up with the H-bridge and the 555 is supplying the PWM.
[noparse][[/noparse] ] Now, if I can only program the BOE-BOT to interface with he Flux Capacitor.
[noparse][[/noparse] ] I dream in SX28 assembler...
Bamse said...
I've had some problem with the programming as well...
All of the sudden it would not find the propeller...
Kept trying to detect the prop a few times and then it start working again...
Weird...
Not really weird. I did something dumb if it failed to detect a prop while going to download (which can happen occasionally) and that failure is only cleared by using "detect propeller" which uses a different code path. Fix in the next release. Sorry for the hassle.
Ok, updated version. Changelog in top post and about box (click on a blank spot on the panel)
Nothing *huge* feature wise.
Right click menu on Tabs for linux version (it's ctrl-click on Macos, but it does not work yet)
Biggest discovery was due to literally hours of debugging on the part of Stevenmess2004. (A thousand Pardons!).
The Parallax font as supplied by the propeller tool is broken, broken, broken on MacOS!
No really! - it reports a character height of zero pixels.
Mac users please check the propeller wiki for the link to a fixed version of the font that works properly on non-windows machines.
Linux users, it works but looks Smile. Use the same font from the Wiki please.
There is now code to detect the faulty font, prevent its use and point you to the download for one that is fixed.
I also found a bug in detecting/downloading repeatedly and hopefully fixed it.
Many thanks to rjo_ and Bamse for reporting the problem.
Again, so many thanks to stevenmess2004 for the assistance in remotely debugging the crash on Mac.
Now, if the compiler crashes for you with an unsaved file, please (if you can) email me either the code that crashed it *or* a copy of the bst.recover file *before* you restart the ide. This will allow me to debug and fix the crash.
If you can get it to crash, I *really* want to fix it. Linux or MacOS.. no matter what version.
Ok, updated version. Changelog in top post and about box (click on a blank spot on the panel)
Nothing *huge* feature wise.
This was a huge fix for me. I was having the same problem Stevenmess2004 was having. I can verify that this new version plus the repaired Parallax font, fixed things for me. I have not tried to program a propeller, but it compiled all my current SPIN code without error.
On a G5... using screen as serial terminal... first time works fine. But after exiting screen with control-a control-\ and exiting the terminal by quitting... bst can no longer find the prop... even though the bst alert window specifies the correct port that it cannot find... ie. "failed to detect prop on port (the correct port)"
This is new... not as it was in .003.
Quitting bst and restarting bst... still cannot detect Prop...
Only recourse seems to be restarting the Mac...
looks like a temporary file is now being created by bst or appleevents and left open and can't be accessed by bst on restarting bst... I know nothing about the innards here... but my telepathic sense tells me that if bst is directly causing this, you can create a boolean that you set on the first detecting the Prop... then check that boolean and if it is set... first close the offending file from bst before trying to detect the prop again... this might fix it... sort of.
The other way would be to eliminate the file using the MacOSX terminal after terminating the Screen but before quitting the terminal... but then we would have to have a way to find the offending file...
I don' know enough about appleevents to know if it is the offending agent here... If so ... that would mean that you might never find the bug.
Crash report... multiple failed tries to detect prop as described above... and then doing something else (like writing to the forum) causes bst to crash.
On a G5... using screen as serial terminal... first time works fine. But after exiting screen with control-a control-\ and exiting the terminal by quitting... bst can no longer find the prop... even though the bst alert window specifies the correct port that it cannot find... ie. "failed to detect prop on port (the correct port)"
This is new... not as it was in .003.
Quitting bst and restarting bst... still cannot detect Prop...
brad... just saw your other note... Sounds like you have already solved the directory issue and that I just didn't see it... I won't have time to do much til tonight.
I'm pretty sure that I don't have the skills required to make much of bstc... but I would like to look at it... sort of like a tourist looking at a monument[noparse]:)[/noparse]
I'm pretty sure that I don't have the skills required to make much of bstc... but I would like to look at it... sort of like a tourist looking at a monument[noparse]:)[/noparse]
Rich, if you can script bst, then bstc will be a walk in the park for you. Really..
Want to compile and download a file?
bstc -p0 Fnarf.spin
Want to compile and download to EEProm?
bstc -p2 Fnarf.spin
Want to compile a file that requires propeller library files?
bstc -p0 -L /home/brad/Prop-Library Fnarf.spin
Nothing more complex. Surely a heck of a lot easier than using applescript to drive a graphical program [noparse];)[/noparse]
Oh... and you can compile files that reside in different directories without having to change into that..
Thanks Brad. This seems to work on my MacBook. I have a Propeller project to work on this next week, so it'll get exercised. It's really a pleasure to be able to work directly under MacOS rather than having to run Windows under VMWare.
Brad... search path in compiler prefs works... I can now copy and paste to bst and compile to EEPROM without additional hickups.
If you don't hear anything from me in the next day or two it will be because there are some things I've been dying to try out on my Mac using BST [noparse]:)[/noparse]
Thanks Brad,
I'll have to wait until to night to give the new version a try though...
I was about to upload DataSette.binary to my protoboard but could not figure out how to upload a binary or eeprom file...
This is a very low priority for me but it would be nice to be able to do this in the future...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Living on the planet Earth might be expensive but it includes a free trip around the sun every year...
Experience level:
[noparse][[/noparse] ] Let's connect the motor to pin 1, it's a 6V motor so it should be fine.
[noparse][[/noparse] ] OK, I got my resistors hooked up with the LEDs.
[noparse][[/noparse]X] I got the Motor hooked up with the H-bridge and the 555 is supplying the PWM.
[noparse][[/noparse] ] Now, if I can only program the BOE-BOT to interface with he Flux Capacitor.
[noparse][[/noparse] ] I dream in SX28 assembler...
Bamse said...
Thanks Brad,
I'll have to wait until to night to give the new version a try though...
I was about to upload DataSette.binary to my protoboard but could not figure out how to upload a binary or eeprom file...
This is a very low priority for me but it would be nice to be able to do this in the future...
mmm you need bstl then [noparse];)[/noparse]
Seriously.. I'll add a binary upload to the next version. Being able to compile a file, it never even occurred to me to want to upload a pre-compiled binary.
I'll start keeping error reports, and code for you.. [noparse]:)[/noparse]
Question, does this version allow for double-clicking spin files and opening
them in the editor? I've got BST opening when I click on a .spin, but doesn't
open the file. Plans for this?
Oldbitcollector said...
I'll start keeping error reports, and code for you.. [noparse]:)[/noparse]
I'd *really* appreciate that. It makes it so much easier for me if you can throw a spin file my way and say "this crashes".
I know the compiler still has some crash bugs in it, and I'd really like to get them fixed.
Unfortunately it's quite a complex bit of code. I'm not a very clever code architect.
Oldbitcollector said...
Question, does this version allow for double-clicking spin files and opening
them in the editor? I've got BST opening when I click on a .spin, but doesn't
open the file. Plans for this?
Mac or Linux? Yes I have plans for both, but I need to get the file associations sorted out properly.
It *should* open them in Linux.. but it will likely do dumb things like open one copy of bst for each copy clicked at the moment.
For Linux, I'll certainly make sure it does it before I release the next version OBC. Mac version is a little more complex to get that to work (really, really, really), but I will certainly try my hardest to make sure I get it sorted asap.
Mike Green said...
Thanks Brad. This seems to work on my MacBook. I have a Propeller project to work on this next week, so it'll get exercised. It's really a pleasure to be able to work directly under MacOS rather than having to run Windows under VMWare.
Thanks Mike, I look forward to your feedback.
Yes, I wrote it for linux initially as I was getting tired of booting virtualbox and XP to run propeller tool. Native is much nicer.
Comments
Got to try it out later tonight...
The only thing I'm missing so to say is the indentation markers to see what code belongs to which block...
Awesome job...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Living on the planet Earth might be expensive but it includes a free trip around the sun every year...
Experience level:
[noparse][[/noparse] ] Let's connect the motor to pin 1, it's a 6V motor so it should be fine.
[noparse][[/noparse] ] OK, I got my resistors hooked up with the LEDs.
[noparse][[/noparse]X] I got the Motor hooked up with the H-bridge and the 555 is supplying the PWM.
[noparse][[/noparse] ] Now, if I can only program the BOE-BOT to interface with he Flux Capacitor.
[noparse][[/noparse] ] I dream in SX28 assembler...
/Bamse
That bit is part of the syntax highlighter code, and I've barely sketched out the skeleton yet. Once I get the core reliable and working that is next on the agenda.
It will happen, just not fast I'm sorry to say..
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Finally got home and had a chance to work with it[noparse]:)[/noparse]
I should begin by saying that I didn't believe that bst on a Mac was even possible... so imagine my delight!!!!
bst is now scriptable!!!!
Proof:
tell application "bst"
activate
end tell
tell application "System Events"
if UI elements enabled then
tell process "bst.osx"
set frontmost to true
click menu item "Compile and Load EEPROM" of menu 1 of menu bar item "Compile" of menu bar 1
--get every action of menu item "Compile and Load EEPROM" of menu 1 of menu bar item "Compile" of menu bar 1
end tell
end if
end tell
this applescript causes bst to compile and load the eeprom...AND that is good enough for me[noparse]:)[/noparse]
Nothing funky... computer is happy.
Minor issues
bst doesn't find the Prop until I tell it to... remember I'm on a Mac G5 10.4.1.1.1.1.1...... so there could be an issue that you could easily
ignore... it is really a legacy puter[noparse]:)[/noparse]
my terminal program can open bst but the file to be loaded isn't... doesn't matter if it is in the same directory with bst or not.
Since applescript works just fine... I can work around this quite nicely... so please satisfy everyone else first.
haven't had a chance to hook up more than one prop yet... but I'm drooling at the thought.
Pace yourself... I'm really excited about this and I don't want you to burn yourself out.
Thanks... thanks.... thanks
Rich
I found out last night that OSX uses some weird Smile drag'n'drop events to load files from the finder rather than command line entries.
If you call bst.osx directly (located inside bst.app) it will open a file from the command line for you. I've added fixing that from Finder to my list though.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Thanks again... calling bst.osx doesn't do it...
In one of your answers you said that the mac screen can act as a serial terminal...
screen /dev/ttySO 9600
This doesn't work for me either... can't find ttySO
but this applescript does work:
tell application "Terminal"
do script with command "screen /dev/tty.usbserial-A1001gJp"
set number of rows of window 1 to 100
set number of columns of window 1 to 80
set background color of window 1 to "black"
set normal text color of window 1 to "green"
set custom title of window 1 to "SerialOut"
end tell
May God bless you and keep you well.
Rich
No.. it won't if your serial port is not on /dev/ttyS0.
Based on what you wrote below this, this should work for you.
screen /dev/tty.usbserial-A1001gJp 9600
Glad you found a solution in any case.
As for the bst.osx..
./bst.osx /Users/Brad/test.spin
Opens the file right up here.. *but* a proportion of the time I can't focus the bst window. It displays but won't accept mouse clicks..
Can't say I'm not learning alot about the peculiarities of OSX [noparse];)[/noparse]
What did you mean by this bit?
if you fire it straight up and click "Detect Propeller" does it not locate the port straight off?
If not, when you open the ports box, what does it locate?
No such thing as a "Legacy Computer" for me, which is why I'm now working on Win95 support. If I can get software to run on it, I want it running as well as it does on any other platform.
I've got a 10.4.11 G4 at home, so I can test on that anyway.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
The peculiarities of OSX run deep... that's why: "if something works... don't touch it[noparse]:)[/noparse]"
I only have one problem for which I can't think of a workaround... so things are beautatious[noparse]:)[/noparse]
First to answer your question: When I start bst... I first have to do a "detect Prop" before I can compile ... I don't remember if this is how it was in the prior version of bst or not. It isn't really a problem... more of a "feature."
Also when I use applescript to tell bst to compilem the current window it works fine... but before I can tell it to compile again I have to tell it to 'detect prop" again... again this not a much of a problem.
When I switch from one window to another... I have to do another "detect Prop."
I have a feeling that there is a common source for all of this, but I also have a the fear that if you chase this kind of thing into the rat's nest you'll never come out.
I'm using a bash shell... and for anyone else that reads this thread... as with the serial terminal in XP... you have to exit the terminal to give the port back to bst... in order for bst to be able to see the PROP. To exit out of the serial terminal created by the command line Screen you simply hold the commandkey down and strike the "a" key... followed by a commandkey down with the backslash key {"\")
There is one issue that I don't yet have a workaround for... when I have a plain text document... saved as a spin file... I can load the file into bst and compile... no problem. But if I open the same document in TextEdit and then copy and paste it into bst... I get a compile error.
I can even create the file in textedit... save it and then open it with bst and everything is fine... but the same file copied from textedit and pasted into bst throws a compile error... this is a problem... since my workarounds for the command line issues have to do with controlling textedit and then automatically copying and pasting the results into a bst window for compilation...
I am hoping that you or someone else will know of a way to do this sort of thing without having to modify your code.
By the way... from the number of views that this thread is getting, I would say that you are on a hot topic with bst[noparse]:)[/noparse]
Thanks again
Rich
Ok, what happens if you don't "detect Prop" before you compile? Does it do anything? Give an error message?
Does it do this when you are using it normally with the mouse or only when you script it?
What _is_ the compile error?
I just tried it here and the error I got was that it can't locate objects.
This makes perfect sense as when you paste code into the window, it does not know where it has come from on disk, and therefore it has no idea which directory to look in for the objects that might go along with it.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
This morning I started out getting some errors.... in a variety of ways. But at the moment, I don't get any errors except when I paste a file into bst that has objects in them... which makes perfect sense.
I also noticed earlier that if I waited after starting up bst... things worked ok... and there seems to be a lag between my keyboard and my screen...
I'm thinking my puter has a problem.
time for a virus scan... where did I put my norton's
rich
Just to be complete... since I'm working on a G5 and this might be peculiar to it.
(I restarted my computer... the keyboard latency is fine. Playing with appleevents can really screw up a computer: )
I manually start bst... open a file containing objects... compile to EEProm... no problem first time... after playing around for a while sometimes it says it can't find prop.
I then open the same file in textEdit and copy all, tjem select all text in my window (containing the manually loaded spin file) and paste...
Then I try to manually compile to eeprom... I get "No Prop Detected on port (name of my port)."...BUT if I just try to compile to eeprom again it works fine. And if start bst and do a "detect Prop" first, there is no problem.
Since I'm working on automation... I can easily to a detect Prop every time... so this is nothing.
If I paste a spin file containing objects into an empty window, I get a compile error... as expected and explained by you.
BUT the good news is that if I paste the same spin file into a window with a spin file (with objects) previously loaded from bst into bst... then the object reference doesn't cause a problem... which is the workaround for this particular issue[noparse]:)[/noparse]
Maybe you could include BST's root as the default object directory?
Ok, the prop detection issues I'll work on. It's entirely possible there is a timing glitch on powerpc.
I've tested it extensively, but it's entirely possible I'm missing something. The propeller can be quite sensitive about it's various time delays.
As for the issue of bst's root. Is that the directory bst resides in, or the directory you start it from?
If it's the former you can just add it to the compiler search path in the compiler prefs dialog.
If it's the latter, perhaps I can look at how I might do that.
I still wonder if you are automating it to that degree, if you would not be better using bstc.. do you *need* the editor components?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Only complaint being that it dies very badly when it tried to compile bad code.
Looking forward to your next release!
OBC
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
New to the Propeller?
Getting started with a Propeller Protoboard?
Check out: Introduction to the Proboard & Propeller Cookbook 1.4
Updates to the Cookbook are now posted to: Propeller.warrantyvoid.us
Got an SD card connected? - PropDOS
Ooo.. can you send me the bad code that kills it? I can't fix it unless I can reproduce it.
I've added a feature or two, so I'm kinda getting ready for another release soonish, but I'd like to be able to fix this crash bug before I do that now.
Did the autosave work for you when it crashed?
if you could send the crash inducing code to brad at fnarfbargle dot com, or post it here I'd be really, really appreciative.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
All of the sudden it would not find the propeller...
Kept trying to detect the prop a few times and then it start working again...
Weird...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Living on the planet Earth might be expensive but it includes a free trip around the sun every year...
Experience level:
[noparse][[/noparse] ] Let's connect the motor to pin 1, it's a 6V motor so it should be fine.
[noparse][[/noparse] ] OK, I got my resistors hooked up with the LEDs.
[noparse][[/noparse]X] I got the Motor hooked up with the H-bridge and the 555 is supplying the PWM.
[noparse][[/noparse] ] Now, if I can only program the BOE-BOT to interface with he Flux Capacitor.
[noparse][[/noparse] ] I dream in SX28 assembler...
/Bamse
Not really weird. I did something dumb if it failed to detect a prop while going to download (which can happen occasionally) and that failure is only cleared by using "detect propeller" which uses a different code path. Fix in the next release. Sorry for the hassle.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Nothing *huge* feature wise.
Right click menu on Tabs for linux version (it's ctrl-click on Macos, but it does not work yet)
Biggest discovery was due to literally hours of debugging on the part of Stevenmess2004. (A thousand Pardons!).
The Parallax font as supplied by the propeller tool is broken, broken, broken on MacOS!
No really! - it reports a character height of zero pixels.
Mac users please check the propeller wiki for the link to a fixed version of the font that works properly on non-windows machines.
Linux users, it works but looks Smile. Use the same font from the Wiki please.
There is now code to detect the faulty font, prevent its use and point you to the download for one that is fixed.
I also found a bug in detecting/downloading repeatedly and hopefully fixed it.
Many thanks to rjo_ and Bamse for reporting the problem.
Again, so many thanks to stevenmess2004 for the assistance in remotely debugging the crash on Mac.
Now, if the compiler crashes for you with an unsaved file, please (if you can) email me either the code that crashed it *or* a copy of the bst.recover file *before* you restart the ide. This will allow me to debug and fix the crash.
If you can get it to crash, I *really* want to fix it. Linux or MacOS.. no matter what version.
Thanks all [noparse]:)[/noparse]
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
This was a huge fix for me. I was having the same problem Stevenmess2004 was having. I can verify that this new version plus the repaired Parallax font, fixed things for me. I have not tried to program a propeller, but it compiled all my current SPIN code without error.
Thanks Brad!
On a G5... using screen as serial terminal... first time works fine. But after exiting screen with control-a control-\ and exiting the terminal by quitting... bst can no longer find the prop... even though the bst alert window specifies the correct port that it cannot find... ie. "failed to detect prop on port (the correct port)"
This is new... not as it was in .003.
Quitting bst and restarting bst... still cannot detect Prop...
Only recourse seems to be restarting the Mac...
looks like a temporary file is now being created by bst or appleevents and left open and can't be accessed by bst on restarting bst... I know nothing about the innards here... but my telepathic sense tells me that if bst is directly causing this, you can create a boolean that you set on the first detecting the Prop... then check that boolean and if it is set... first close the offending file from bst before trying to detect the prop again... this might fix it... sort of.
The other way would be to eliminate the file using the MacOSX terminal after terminating the Screen but before quitting the terminal... but then we would have to have a way to find the offending file...
I don' know enough about appleevents to know if it is the offending agent here... If so ... that would mean that you might never find the bug.
Crash report... multiple failed tries to detect prop as described above... and then doing something else (like writing to the forum) causes bst to crash.
Rich
Never give up.
I don't know what this means, exactly.
Initially, I still get a failed to detect prop alert... when I first open bst on G5 and try to detect... but this goes away when I try again.
Rich
Thanks Rich.. I'm on it.. give me a day or two..
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
I'm pretty sure that I don't have the skills required to make much of bstc... but I would like to look at it... sort of like a tourist looking at a monument[noparse]:)[/noparse]
Rich
Rich, if you can script bst, then bstc will be a walk in the park for you. Really..
Want to compile and download a file?
bstc -p0 Fnarf.spin
Want to compile and download to EEProm?
bstc -p2 Fnarf.spin
Want to compile a file that requires propeller library files?
bstc -p0 -L /home/brad/Prop-Library Fnarf.spin
Nothing more complex. Surely a heck of a lot easier than using applescript to drive a graphical program [noparse];)[/noparse]
Oh... and you can compile files that reside in different directories without having to change into that..
bstc -p0 -L /home/brad/Prop-Library /home/brad/Projects/Thermostat/Thermostat_001.spin
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
If you don't hear anything from me in the next day or two it will be because there are some things I've been dying to try out on my Mac using BST [noparse]:)[/noparse]
I'll have to wait until to night to give the new version a try though...
I was about to upload DataSette.binary to my protoboard but could not figure out how to upload a binary or eeprom file...
This is a very low priority for me but it would be nice to be able to do this in the future...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Living on the planet Earth might be expensive but it includes a free trip around the sun every year...
Experience level:
[noparse][[/noparse] ] Let's connect the motor to pin 1, it's a 6V motor so it should be fine.
[noparse][[/noparse] ] OK, I got my resistors hooked up with the LEDs.
[noparse][[/noparse]X] I got the Motor hooked up with the H-bridge and the 555 is supplying the PWM.
[noparse][[/noparse] ] Now, if I can only program the BOE-BOT to interface with he Flux Capacitor.
[noparse][[/noparse] ] I dream in SX28 assembler...
/Bamse
mmm you need bstl then [noparse];)[/noparse]
Seriously.. I'll add a binary upload to the next version. Being able to compile a file, it never even occurred to me to want to upload a pre-compiled binary.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Post Edited (BradC) : 10/10/2008 3:55:55 PM GMT
Question, does this version allow for double-clicking spin files and opening
them in the editor? I've got BST opening when I click on a .spin, but doesn't
open the file. Plans for this?
OBC
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
New to the Propeller?
Getting started with a Propeller Protoboard?
Check out: Introduction to the Proboard & Propeller Cookbook 1.4
Updates to the Cookbook are now posted to: Propeller.warrantyvoid.us
Got an SD card connected? - PropDOS
I'd *really* appreciate that. It makes it so much easier for me if you can throw a spin file my way and say "this crashes".
I know the compiler still has some crash bugs in it, and I'd really like to get them fixed.
Unfortunately it's quite a complex bit of code. I'm not a very clever code architect.
Mac or Linux? Yes I have plans for both, but I need to get the file associations sorted out properly.
It *should* open them in Linux.. but it will likely do dumb things like open one copy of bst for each copy clicked at the moment.
For Linux, I'll certainly make sure it does it before I release the next version OBC. Mac version is a little more complex to get that to work (really, really, really), but I will certainly try my hardest to make sure I get it sorted asap.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Thanks Mike, I look forward to your feedback.
Yes, I wrote it for linux initially as I was getting tired of booting virtualbox and XP to run propeller tool. Native is much nicer.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!