Thanks! Will take a look at it tomorrow with my Stamp BOE. It launches on Mt Lion automatically when I double-click on any .bs2 file! Congrats on a great start.
Heads up to everyone who was having trouble downloading to the BS2 variety of STAMP. I fixed it. Apologies for this one; I lost my BS2 awhile back, so it was the only flavor of STAMP that I didn't test. But I have one now.
Heads up to everyone who was having trouble downloading to the BS2 variety of STAMP. I fixed it. Apologies for this one; I lost my BS2 awhile back, so it was the only flavor of STAMP that I didn't test. But I have one now.
Murat, you're the last guy who should be in a hardware-impoverished position. Please let me know what you need and I'll FedEx you the greatest care package you've ever received.
Thank you so much for what you're doing with MacBS2!
Heads up to everyone who was having trouble downloading to the BS2 variety of STAMP. I fixed it. Apologies for this one; I lost my BS2 awhile back, so it was the only flavor of STAMP that I didn't test. But I have one now.
Report #1: Syntax Coloring changes corrupt code text in the editor view
====================================================
A) What steps will reproduce the problem?
1. Bring up any .bs2 file that contains code and comments 2. Un-select "Syntax Coloring" from the View menu, note how code text becomes al green 3. Re-select "Syntax Coloring" from the View men and examine code text
What is the expected behavior (output)? Should return to correct syntax coloring of the code text
C) What do you see instead? Text gets corrupted with repeated patterns of reserved words and miss-coloring of text. See attached screenshots.
D) Classify the bug as one of the following:
1. Show Stopper as it actually corrupts the user's text, if the file is saved in the corrupted condition.
E) Application Version and Platform:
Version macbs2 version 3.0.4, May 2, 2013
Platform
OpSys: OpSys-Mac
Specify Platform OS Version and 32 or 64 bit. For example:
Mac OSX (64 bit Mountain Lion, 10.8.3)
Provide any links or additional information below if possible. See before and after images.
Before, I had to use Parallels Desktop to have an OSX 10.6 Snow Leopard to use macbs2 on my Macbook Pro with Mountain Lion (I know, I could have used windows and the Basic Stamp Editor, but being a Mac and Linux user, I don't really like Windows).
When I try to open (with the new macbs2) some .bs2 files I made with the old macbs2, it doesn't always work. For 2/3 of the files, it's fine, but for the other 1/3, I get "The document “nameofthefile.bs2” could not be opened." Is it normal?
What steps will reproduce the problem? Open some "old macbs2" files. What is the expected behavior (output)? Open the file correctly. What do you see instead? "The document “nameofthefile.bs2” could not be opened." (for about 1/3 of the documents)
Application version and platform: macbs2 3.0.5 / Macbook Pro Retina mi-2012 2.3 gHz intel core i7 (quadricore) with OS X 10.8.3 (12D78) Mountain Lion.
To get around this issue in the interim, drag the .bs2 files that will not open in MacBS2 to a text editor (ex: TextEdit on Mac OS X) and they will open as text files. Select all of the code text and Copy that to the Clipboard as you would any text. Open a New code document with MacBS2 and paste the copied code to create a new version of your file.
Report #2: Adding "."'s in succession causes editor to create ellipse char and corruption of reserved words in the source =======================================================================================
A) What steps will reproduce the problem?
1. Bring up any .bs2 file that contains code and DEBUG statements 2. Add a few (3-6) "." (period) characters to a DEBUG statement 3. Notice that after 3 "." characters are entered, the ditor quickly replaces them with a single ellipse character 4. Shortly after the "..." is replaced with an ellipse character " " notice what happens to the entire source text
What is the expected behavior (output)? A) "..." should not be turned into an ellipse character the reserved words and other text should NOT become corrupted
C) What do you see instead? Text gets corrupted with repeated patterns of reserved words and miss-coloring of text, similar to my bug report #1 (which was fixed in this most-recent version). SEE ATTACHED MOVIE FILE (zipped).
Screenshot:
D) Classify the bug as one of the following:
1. Show Stopper as it actually corrupts the user's text, if the file is saved in the corrupted condition.
Comments
Thanks! Will take a look at it tomorrow with my Stamp BOE. It launches on Mt Lion automatically when I double-click on any .bs2 file! Congrats on a great start.
dgately
However I do hope you and parallax continue to host and link to the Older 10.5 ish compatible version too for us older mac users ....
IMO PPC IS dead so cutting off 10.4 as a mac user would not be issue
m any
Peter..
-- Tracy
Thank You!
Amanda
Available at: http://muratnkonar.com/otherstuff/macbs2-experimental/downloads.shtml
_murat
Murat, you're the last guy who should be in a hardware-impoverished position. Please let me know what you need and I'll FedEx you the greatest care package you've ever received.
Thank you so much for what you're doing with MacBS2!
Ken Gracey
Bug report on MacBS2... http://forums.parallax.com/showthread.php/133804-Support-OS-X-10.7-Lion/page2
Report #1: Syntax Coloring changes corrupt code text in the editor view
====================================================
A) What steps will reproduce the problem?
1. Bring up any .bs2 file that contains code and comments
2. Un-select "Syntax Coloring" from the View menu, note how code text becomes al green
3. Re-select "Syntax Coloring" from the View men and examine code text
C) What do you see instead? Text gets corrupted with repeated patterns of reserved words and miss-coloring of text. See attached screenshots.
D) Classify the bug as one of the following:
1. Show Stopper as it actually corrupts the user's text, if the file is saved in the corrupted condition.
E) Application Version and Platform:
Version
macbs2 version 3.0.4, May 2, 2013
Platform
OpSys: OpSys-Mac
Specify Platform OS Version and 32 or 64 bit. For example:
Mac OSX (64 bit Mountain Lion, 10.8.3)
Provide any links or additional information below if possible. See before and after images.
<http://muratnkonar.com/otherstuff/macbs2-experimental/downloads.shtml>
_murat
Before, I had to use Parallels Desktop to have an OSX 10.6 Snow Leopard to use macbs2 on my Macbook Pro with Mountain Lion (I know, I could have used windows and the Basic Stamp Editor, but being a Mac and Linux user, I don't really like Windows).
When I try to open (with the new macbs2) some .bs2 files I made with the old macbs2, it doesn't always work. For 2/3 of the files, it's fine, but for the other 1/3, I get "The document “nameofthefile.bs2” could not be opened." Is it normal?
What steps will reproduce the problem? Open some "old macbs2" files.
What is the expected behavior (output)? Open the file correctly.
What do you see instead? "The document “nameofthefile.bs2” could not be opened." (for about 1/3 of the documents)
Application version and platform: macbs2 3.0.5 / Macbook Pro Retina mi-2012 2.3 gHz intel core i7 (quadricore) with OS X 10.8.3 (12D78) Mountain Lion.
To get around this issue in the interim, drag the .bs2 files that will not open in MacBS2 to a text editor (ex: TextEdit on Mac OS X) and they will open as text files. Select all of the code text and Copy that to the Clipboard as you would any text. Open a New code document with MacBS2 and paste the copied code to create a new version of your file.
dgately
=======================================================================================
A) What steps will reproduce the problem?
1. Bring up any .bs2 file that contains code and DEBUG statements
2. Add a few (3-6) "." (period) characters to a DEBUG statement
3. Notice that after 3 "." characters are entered, the ditor quickly replaces them with a single ellipse character
4. Shortly after the "..." is replaced with an ellipse character " " notice what happens to the entire source text
C) What do you see instead? Text gets corrupted with repeated patterns of reserved words and miss-coloring of text, similar to my bug report #1 (which was fixed in this most-recent version). SEE ATTACHED MOVIE FILE (zipped).
Screenshot:
D) Classify the bug as one of the following:
1. Show Stopper as it actually corrupts the user's text, if the file is saved in the corrupted condition.
E) Application Version and Platform:
Versionmacbs2 3.0.5 may 9, 2013
Platform
OpSys: OpSys-Mac
Specify Platform OS Version and 32 or 64 bit. For example:
Mac OSX (64 bit Mountain Lion, 10.8.3)
Provide any links or additional information below if possible. See before and after images.
I reported the bug and Murat Konar answered: "I believe the problem has to do with double-byte characters such as '