TChapman said...
I noticed some things tonight new, clicking on the "+" fold down icon was folding blocks several blocks lower. It seems that deleting lines, or parts of lines of a block is weirding out the fold feature as described, but this is a guess. I did notice that once I hit Fold All Blocks it seems to rid the strange problem of blocks getting un/folded lower than the block I am clicking on.
Yep, I can reproduce this with the block folder. Deleting lines causes folded blocks below those lines to randomly pop open. An *interesting* "feature" I'd say [noparse]:)[/noparse]
At least it's not a destructive feature <whew> unlike your XP crash bug.
I have an item for the bst "wish list", in case there is ever a time when you are really bored and looking for things to add:
Double clicking anywhere left of the margin(in the line numbers area) within a code block will fold that block. In a few cases there are some really long blocks that require scrolling to get back to the +, this would be a nice feature. Sure you could fold all but my habits are such that I will often have 2 or 3 blocks only open and go back and forth between them making changes, so folding all isn't the best option sometimes.
I know how to reproduce that "paint with white over the name of the files" (Mac OS 10.5.5)
Load a file from the left list and when loaded... scroll with the wheel (not with the scroll bar): here are two screen chots.
Edit: and move asap the mouse over the text editor... it will just happen or not, it is not necessary to scroll. Not on all files it does that, though.
I know how to reproduce that "paint with white over the name of the files" (Mac OS 10.5.5)
Load a file from the left list and when loaded... scroll with the wheel (not with the scroll bar): here are two screen chots.
Edit: and move asap the mouse over the text editor... it will just happen or not, it is not necessary to scroll. Not on all files it does that, though.
Oh Nice work. I can reproduce this reliably now. Unfortunately it's a bug in the widgetset of the tools I'm using, so it's likely to take me quite a while to track down and nail. It's not likely to happen anytime soon I'm afraid. The bug with the cursor not changing as it leaves the right side of the editor is a bug in the toolset also, but that one might be a bit easier to fix. Will keep looking at both of them anyway.
@TChapman, I've added that feature such that you click on the [noparse][[/noparse]+] or anywhere along the grey line and the whole block will fold up.
Brad, New feature request. Can you put a "Start at Top" checkbox in the find command, and a beep when it hits the end of the file without finding anything?
Also, a highlight and triple-blink of the found item would help me find things fast.
Chuck Rice said...
Brad, New feature request. Can you put a "Start at Top" checkbox in the find command, and a beep when it hits the end of the file without finding anything?
Also, a highlight and triple-blink of the found item would help me find things fast.
Checkbox : Can do
Beep : Perhaps, maybe, possibly
Highlight flash : Can do
The problem with the beep is it depends on me being able to make it work reliably across all platforms. I'll certainly look into it.
This one might take a while as I'll have to rebuild the find/replace forms from the ground up (I'm using toolkit supplied forms at the moment), but I'll get it done. It's probably something I'd use myself but have never got around to looking into.
@OBC, great news on the new install. I actually go to a lot of pains to ensure that bst minimises external dependencies. It also should run on any version of GTK2 from 2.8->current.
To put that in perspective, Ubuntu Dapper Drake LTS (6.06) is using 2.8 (I test on it before I release). I also test on Ubuntu 8.10 (GTK2 2.14) now (thanks to a certain cut and paste bug). Personally I develop on Ubuntu 8.04 (GTK2 2.12) and cross compile to windows and OSX from there.
Brad did you alter copy and paste on 13? When I paste (XP), it leaves the cursor on the line below the paste line.
Also, on the Parallax version, if you are trying to copy two lines, and you take your mouse the the end of the bottom line to copy, and drag it up to the beginning of the top line to copy, it will grab everything in between in the highlighted copy. On Bst, if for example your first line is longer than the second line, the text on the first line that is beyond the text on the second line is not highlighted or copied, things get left out. To solve it, I can go to the right of all text on each line, and start dragging from the second line to the left and it will highlight all the stuff properly and it can all be copied. Not a big deal once you get used to it.
I think the copy and paste is strange in another regard:
When you copy two lines for example, and paste the two lines into an open line, normally it should make room and slide the other lines down, but it is sliding the existing line below the open space over to the right, like below:
Copy these lines:
asdf asdf asdf asdf
asdf asdf asdf asdf
Here is a space you want to copy to:
dfgh dfgh dfgh
< start paste here
dfgh dfgh dfgh
The result is:
asdf asdf asdf asdf
asdf asdf asdf asdf dfgh dfgh dfgh
But should be:
asdf asdf asdf asdf
asdf asdf asdf asdf
dfgh dfgh dfgh
The solution is to first create a bigger space to paste into manually.
Post Edited (TChapman) : 11/20/2008 7:09:26 AM GMT
TChapman said...
Brad did you alter copy and paste on 13? When I paste (XP), it leaves the cursor on the line below the paste line.
Also, on the Parallax version, if you are trying to copy two lines, and you take your mouse the the end of the bottom line to copy, and drag it up to the beginning of the top line to copy, it will grab everything in between in the highlighted copy. On Bst, if for example your first line is longer than the second line, the text on the first line that is beyond the text on the second line is not highlighted or copied, things get left out. To solve it, I can go to the right of all text on each line, and start dragging from the second line to the left and it will highlight all the stuff properly and it can all be copied. Not a big deal once you get used to it.
Ok, I've tried and tried and I can't seem to find a logical reason for this.. but I have an idea.
There are 3 selection modes in the editor
Normal, Line and Column.
Ctrl-Shift-C selects Column
Ctrl-Shift-N selects Normal
Ctrl-Shift-L selects Line (which conflicts with line numbers on and off - so I removed the keystrokes to select that mode, I might have a bug with that)
I wonder if you have inadvertently selected Column Mode or (more likely) I have a bug that is doing that by itself.
Can you try Ctrl-Shift-N to select normal mode and have a play with it?
Column mode is cool as you can select a block of text in a square or rectangle then you can drag it around the editor like you can with Propeller Tool, but it might make things a bit ugly when trying to use it normally.
Otherwise I'm currently out of ideas. Here on XP/Mac/Linux it behaves just like every other normal application does.
Ok great that is the problem, although I was not aware that such an option existed, nor do I recall at any time doing a Ctrl-Shift-X at any time.
I must admit I have not read the entire thread to understand all the options, and there is no mention of the options within the app itself that I am aware of.
Maybe if you had a consolidated list of options posted on the top thread, in the app, or in a read me (which maybe already exist for all I know) then it would reduce dumb questions like my recent one.
TChapman said...
Ok great that is the problem, although I was not aware that such an option existed, nor do I recall at any time doing a Ctrl-Shift-X at any time.
I must admit I have not read the entire thread to understand all the options, and there is no mention of the options within the app itself that I am aware of.
Maybe if you had a consolidated list of options posted on the top thread, in the app, or in a read me (which maybe already exist for all I know) then it would reduce dumb questions like my recent one.
I like those options btw.
Yeah, to be honest I've not documented them anywhere yet. They were options that I've been playing with but not really polished enough to have told people about yet.
The Column mode is Ctrl-Shift-C, so it'd be very easy to hit accidentally when trying to go for ctrl-c I guess. I've been meaning to add the current select mode to the status bar, guess I'd better get that happening.
Glad that was the problem rather than something ugly and deeper.
A manual or something is on the todo list, but it all takes time..
One day I'll get around to a web page or something too.. at the moment i'm kinda just working on getting it all working if you know what I mean.
I do know what you mean. You have opened a can of worms, but hopefully there will be some value that comes out of the effort at some point. Personally, considering the significant hours to write it and the obvious benefits of the app, I think it should have some price tag attached to it.
I don't think you need a manual, but a single sheet of commands and a short one line description of each preference or option would maybe save you some headaches chasing down non existent issues, my case above for example.
Brad, another "would be nice to have" feature. I often put reference links to web pages where I did the research when adding features. For example
'' Calculate distance between two lat/long pairs using Haversine method.
'' reference: http://www.movable-type.co.uk/scripts/latlong.html
It would be nice if any string starting with http://xxxx... would magically become clickable or option-clickable to take me to the web page. Bug fixes are more important, but if it is easy... [noparse]:)[/noparse]
It would be nice if any string starting with http://xxxx... would magically become clickable or option-clickable to take me to the web page. Bug fixes are more important, but if it is easy... [noparse]:)[/noparse]
Something I've thought about on and off actually, but not in the context of the spin files. I'll certainly look into it. Again, it comes up against needing to find a nice cross-platform way of launching a web browser neatly. I'll add it to the todo list in any case.
I'm 100 % with Oldbit, especially if the option includes some way to send a bill in an envelope, since I do not use (read: have no idea about, nor interest in) paypal. I was going to suggest it per pm .
Thanks guys, I really appreciate that. I'm just not geared up for that kind of thing. Living where I do, quite often anything of value in the mail gets "screened" and often just goes "missing".
I'm more than happy that you get some value from the stuff, if I ever get across to the States a drink would do the job nicely.
and to my delight and surprise the software seems to be working,
up to the point of detecting (and connecting to) the propeller
(ie Propeller Proto Board & Propeller Plug, both from Parallax).
19 clicks out of 20 of the F7 key "detect propeller" result in
Failed to detect Propeller on Port /dev/ttyS3
but every once in a while it does detect "Detected Propeller Version : 1 OK"
but immediately after, pressing F7, F10 (compile to RAM), or F11 (compile to EEPROM)
brings up the "Failed to detect Propeller on Port /dev/ttyS3" message again, with
the accompanying message "Serial Incomplete Buffer Send! Wanted 258 got -1"
in the terminal screen.
Any ideas? I've changed usb cables, with identical results.
Well, it's trying to detect the propeller on /dev/ttyS3 which is not a USB-serial port. It sounds like perhaps your USB-serial device is going away or unreliable.
From a terminal try
ls -la /dev/ttyUSB*
and see what it says. Mine comes up with /dev/ttyUSB0 here.
I have had trouble with my prop-plug lately my Ubuntu 8.04 kernel (when I plug it in most of the time I have to type "lsusb" in a console to get it to detect properly) but it works flawlessly on my laptop and all other machines I have around. I've been meaning to compile a new kernel for that box to stop it happening.
Having a look at dmesg will give you the plug/unplug messages for the prop-plug / dev board and may lend some insight into what is happening.
When you Compile and Load or Compile and Load EEPROM, the progress window width is too small. This makes the progress bar get a scroll bar, and the scroll barcovers the progress bar. Hard to see since it is normally so fast.
I'm getting an "Access Violation" when I have all blocks folded, unfold a single block, then try to re-fold it.
It seems to work in spite of the error.
Oldbitcollector said...
I'm getting an "Access Violation" when I have all blocks folded, unfold a single block, then try to re-fold it.
It seems to work in spite of the error.
OBC
Yeah, I found quite a few bugs in the highlighter since the last release. I think I have most of them nailed now but the next release will be tested a little more thoroughly [noparse]:)[/noparse]
It will continue to work as long as you accept the errors, but it leaks ~32 bytes of ram each time it happens.
I never thought the block folding would be so popular! I use it a lot myself though.
@Chuck, I'll make sure the dialogs are sized correctly next time around. Each OS has slightly different sizing for its widgets (Even between OSX 10.4 and 10.5 believe it or not) so its entirely possible I missed some in my testing [noparse]:)[/noparse]
New release is still a few days away. Still got some bits that need some polish (and the occasional Valgrind to find those memory leaks)
On the OSX front, with some significant help from a Carbon Guru I've managed to "work around" the ugly buttons in the config dialogs, so they at least now look like Apple buttons.
I've been reading the Apple Human Interface Guidelines (which are extremely comprehensive) and given this application is a single main-window app not unlike system preferences (One main window per application only) then closing the main window with the little red button in the corner should actually terminate the application. If I allowed closing the main window with the red button and leaving the menu bar active the application would have zero functionality, so by all accounts the current behaviour is fairly correct.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
TChapman said...
On XP .12 was crashing, often it says a popup error that says "press continue if you want to risk......". If I press continue, things seem ok though.
I also got the same crash tonight too on .13, it usually is having to do with deleting stuff (or backspace maybe I forget what does it).
Ok, I've just found this crash. I've not found the cause yet (it's very deep inside the editor component) however I at least have a workaround to stop it crashing.
@OBC this is the same problem you are seeing with block folding also.
I'll certainly have a fix out as soon as I can.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
BardC said...
@Chuck, I'll make sure the dialogs are sized correctly next time around. Each OS has slightly different sizing for its widgets (Even between OSX 10.4 and 10.5 believe it or not) so its entirely possible I missed some in my testing [noparse]:)[/noparse]
If it serves as consolation.. the same is true for Java programs that use Swing! (was it not write once (pain)run anywhere ?) :-(
Comments
Yep, I can reproduce this with the block folder. Deleting lines causes folded blocks below those lines to randomly pop open. An *interesting* "feature" I'd say [noparse]:)[/noparse]
At least it's not a destructive feature <whew> unlike your XP crash bug.
Ta [noparse]:)[/noparse]
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Double clicking anywhere left of the margin(in the line numbers area) within a code block will fold that block. In a few cases there are some really long blocks that require scrolling to get back to the +, this would be a nice feature. Sure you could fold all but my habits are such that I will often have 2 or 3 blocks only open and go back and forth between them making changes, so folding all isn't the best option sometimes.
I know how to reproduce that "paint with white over the name of the files" (Mac OS 10.5.5)
Load a file from the left list and when loaded... scroll with the wheel (not with the scroll bar): here are two screen chots.
Edit: and move asap the mouse over the text editor... it will just happen or not, it is not necessary to scroll. Not on all files it does that, though.
Post Edited (Ale) : 11/19/2008 9:03:00 AM GMT
Oh Nice work. I can reproduce this reliably now. Unfortunately it's a bug in the widgetset of the tools I'm using, so it's likely to take me quite a while to track down and nail. It's not likely to happen anytime soon I'm afraid. The bug with the cursor not changing as it leaves the right side of the editor is a bug in the toolset also, but that one might be a bit easier to fix. Will keep looking at both of them anyway.
@TChapman, I've added that feature such that you click on the [noparse][[/noparse]+] or anywhere along the grey line and the whole block will fold up.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Also, a highlight and triple-blink of the found item would help me find things fast.
Had to reload due to failing hard drive.. BST also works perfectly under Xubuntu as well..
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
Checkbox : Can do
Beep : Perhaps, maybe, possibly
Highlight flash : Can do
The problem with the beep is it depends on me being able to make it work reliably across all platforms. I'll certainly look into it.
This one might take a while as I'll have to rebuild the find/replace forms from the ground up (I'm using toolkit supplied forms at the moment), but I'll get it done. It's probably something I'd use myself but have never got around to looking into.
@OBC, great news on the new install. I actually go to a lot of pains to ensure that bst minimises external dependencies. It also should run on any version of GTK2 from 2.8->current.
To put that in perspective, Ubuntu Dapper Drake LTS (6.06) is using 2.8 (I test on it before I release). I also test on Ubuntu 8.10 (GTK2 2.14) now (thanks to a certain cut and paste bug). Personally I develop on Ubuntu 8.04 (GTK2 2.12) and cross compile to windows and OSX from there.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Also, on the Parallax version, if you are trying to copy two lines, and you take your mouse the the end of the bottom line to copy, and drag it up to the beginning of the top line to copy, it will grab everything in between in the highlighted copy. On Bst, if for example your first line is longer than the second line, the text on the first line that is beyond the text on the second line is not highlighted or copied, things get left out. To solve it, I can go to the right of all text on each line, and start dragging from the second line to the left and it will highlight all the stuff properly and it can all be copied. Not a big deal once you get used to it.
I think the copy and paste is strange in another regard:
When you copy two lines for example, and paste the two lines into an open line, normally it should make room and slide the other lines down, but it is sliding the existing line below the open space over to the right, like below:
Copy these lines:
asdf asdf asdf asdf
asdf asdf asdf asdf
Here is a space you want to copy to:
dfgh dfgh dfgh
< start paste here
dfgh dfgh dfgh
The result is:
asdf asdf asdf asdf
asdf asdf asdf asdf dfgh dfgh dfgh
But should be:
asdf asdf asdf asdf
asdf asdf asdf asdf
dfgh dfgh dfgh
The solution is to first create a bigger space to paste into manually.
Post Edited (TChapman) : 11/20/2008 7:09:26 AM GMT
Ok, I've tried and tried and I can't seem to find a logical reason for this.. but I have an idea.
There are 3 selection modes in the editor
Normal, Line and Column.
Ctrl-Shift-C selects Column
Ctrl-Shift-N selects Normal
Ctrl-Shift-L selects Line (which conflicts with line numbers on and off - so I removed the keystrokes to select that mode, I might have a bug with that)
I wonder if you have inadvertently selected Column Mode or (more likely) I have a bug that is doing that by itself.
Can you try Ctrl-Shift-N to select normal mode and have a play with it?
Column mode is cool as you can select a block of text in a square or rectangle then you can drag it around the editor like you can with Propeller Tool, but it might make things a bit ugly when trying to use it normally.
Otherwise I'm currently out of ideas. Here on XP/Mac/Linux it behaves just like every other normal application does.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
I must admit I have not read the entire thread to understand all the options, and there is no mention of the options within the app itself that I am aware of.
Maybe if you had a consolidated list of options posted on the top thread, in the app, or in a read me (which maybe already exist for all I know) then it would reduce dumb questions like my recent one.
I like those options btw.
Hey call me Stupid, call me Dumb, may I am Drunk on a barrel of Rum .. I wish I knew ware to down load this IDE
can someone provide me with the link for this software
Badger
Yeah, to be honest I've not documented them anywhere yet. They were options that I've been playing with but not really polished enough to have told people about yet.
The Column mode is Ctrl-Shift-C, so it'd be very easy to hit accidentally when trying to go for ctrl-c I guess. I've been meaning to add the current select mode to the status bar, guess I'd better get that happening.
Glad that was the problem rather than something ugly and deeper.
A manual or something is on the todo list, but it all takes time..
One day I'll get around to a web page or something too.. at the moment i'm kinda just working on getting it all working if you know what I mean.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
I don't think you need a manual, but a single sheet of commands and a short one line description of each preference or option would maybe save you some headaches chasing down non existent issues, my case above for example.
It would be nice if any string starting with http://xxxx... would magically become clickable or option-clickable to take me to the web page. Bug fixes are more important, but if it is easy... [noparse]:)[/noparse]
Something I've thought about on and off actually, but not in the context of the spin files. I'll certainly look into it. Again, it comes up against needing to find a nice cross-platform way of launching a web browser neatly. I'll add it to the todo list in any case.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
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'm more than happy that you get some value from the stuff, if I ever get across to the States a drink would do the job nicely.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
http://www.fnarfbargle.com/bst/013/bst.linux.zip 1227335 Nov 18 16:23
and to my delight and surprise the software seems to be working,
up to the point of detecting (and connecting to) the propeller
(ie Propeller Proto Board & Propeller Plug, both from Parallax).
19 clicks out of 20 of the F7 key "detect propeller" result in
Failed to detect Propeller on Port /dev/ttyS3
but every once in a while it does detect "Detected Propeller Version : 1 OK"
but immediately after, pressing F7, F10 (compile to RAM), or F11 (compile to EEPROM)
brings up the "Failed to detect Propeller on Port /dev/ttyS3" message again, with
the accompanying message "Serial Incomplete Buffer Send! Wanted 258 got -1"
in the terminal screen.
Any ideas? I've changed usb cables, with identical results.
Doug
From a terminal try
ls -la /dev/ttyUSB*
and see what it says. Mine comes up with /dev/ttyUSB0 here.
I have had trouble with my prop-plug lately my Ubuntu 8.04 kernel (when I plug it in most of the time I have to type "lsusb" in a console to get it to detect properly) but it works flawlessly on my laptop and all other machines I have around. I've been meaning to compile a new kernel for that box to stop it happening.
Having a look at dmesg will give you the plug/unplug messages for the prop-plug / dev board and may lend some insight into what is happening.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
When you Compile and Load or Compile and Load EEPROM, the progress window width is too small. This makes the progress bar get a scroll bar, and the scroll barcovers the progress bar. Hard to see since it is normally so fast.
It seems to work in spite of the error.
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
Yeah, I found quite a few bugs in the highlighter since the last release. I think I have most of them nailed now but the next release will be tested a little more thoroughly [noparse]:)[/noparse]
It will continue to work as long as you accept the errors, but it leaks ~32 bytes of ram each time it happens.
I never thought the block folding would be so popular! I use it a lot myself though.
@Chuck, I'll make sure the dialogs are sized correctly next time around. Each OS has slightly different sizing for its widgets (Even between OSX 10.4 and 10.5 believe it or not) so its entirely possible I missed some in my testing [noparse]:)[/noparse]
New release is still a few days away. Still got some bits that need some polish (and the occasional Valgrind to find those memory leaks)
On the OSX front, with some significant help from a Carbon Guru I've managed to "work around" the ugly buttons in the config dialogs, so they at least now look like Apple buttons.
I've been reading the Apple Human Interface Guidelines (which are extremely comprehensive) and given this application is a single main-window app not unlike system preferences (One main window per application only) then closing the main window with the little red button in the corner should actually terminate the application. If I allowed closing the main window with the red button and leaving the menu bar active the application would have zero functionality, so by all accounts the current behaviour is fairly correct.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
Ok, I've just found this crash. I've not found the cause yet (it's very deep inside the editor component) however I at least have a workaround to stop it crashing.
@OBC this is the same problem you are seeing with block folding also.
I'll certainly have a fix out as soon as I can.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
If it serves as consolation.. the same is true for Java programs that use Swing! (was it not write once (pain)run anywhere ?) :-(
Both.. at the bottom of the ctrl-click menu in the editor.
I have not quite got around to hotkeys for them yet.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.