If I understand this correctly, it seems that if you load a basic program that uses the two letters P and I together as a variable (or constant) name, it is wrongly changed into the pi-sign. Right?

Perhaps a bit annoying... especially if PI is 297 and you write something like PK=23+PI and it ends up a little more than 26 instead of the expected result.

I still had 1.5.0 installed and tried it there - PI was not translated to the pi-sign, updating to 2.3.0 and this error appeared.

0 I=1+PI
was changed to
0 I=1+π

IMHO if you want a replacement for the pi-sign it should be {pi} or similar, or maybe "tilde" ~.

Would it be possible to add code file level constants? For example in BASIC I could do this with the comments instead of adding them in the editor's settings:

Code:

!-CONST ADDR_VIDMODE      53270 !-CONST ADDR_SCREENMEM    53272 !-CONST ADDR_CHARMEM      1024

Another suggestion I just thought of would be using the same comment system to declare subs by name. This would work into your renumbering system too:

Code:

!-DECLARE SUB PRINTVARS 110 10 A$ = "test" 20 GOSUB PRINTVARS .. bunch of code 110 PRINT A$ 120 RETURN

-OR- another way to do this would be to create a faux sub label system. The text parser would match up the sub and substitute the line number below the sub declaration. This may be the best way.

Code:

10 A$ = "test" 20 GOSUB PRINTVARS .. bunch of code !- SUB PRINTVARS 110 PRINT A$ 120 RETURN

Also, using 2.3.0 whenever I run a program I get this error:

Code:

System.MissingMethodException: Method not found: 'FastColoredTextBoxNS.VisibleState FastColoredTextBox.NS.Line.get_VisibleState()'.   at CBMPrgGen.Project.SaveOpenFiles()   at CBMPrgGen.Project.SaveProject(Object bSaveFiles)

Thanks! That was the problem.

Is there a way to use the ASM editor to generate DATA statements for BASIC? It would be cool to write small routines in ASM and suck them out into a DATA statement for the BASIC code i'm writing. It would be neat to reverse it too.

Yes, there's a 'generate basic loader' in the tools menu. You can use the memory tool to disassemble memory too.
_________________

Hi! Your app made me pick up an old piece of code I was working on 5 years ago! Good job

The old assembly code was written with relaunch64 and assembled with ACME at the time.
Now I imported it in CBM PGR Studio, changed some of the different formatting stuffs and all seems good but I still get errors when trying to write a PRG of my code.

I don't get it as it used to work before and doesn't now

I have a repeating location comparing routine that branches on when not equal. like this:

Code:

LDA $D001                 SBC #$32                 LSR                 LSR                 LSR                 CMP #$01                 BNE NOT1                 LDA #<RY1                 STA WELKERY+1                 LDA #>RY1                 STA WELKERY+2                 JMP XROWREAD NOT1        CMP #$02                 BNE NOT2                 LDA #<RY2                 STA WELKERY+1                 LDA #>RY2                 STA WELKERY+2                 JMP XROWREAD NOT2        CMP #$03                 BNE NOT3                 LDA #<RY3                 STA WELKERY+1                 LDA #>RY3                 STA WELKERY+2                 JMP XROWREAD NOT3        CMP #$04 etc.

This works fine, until I get to NOT0B, then it says: Invalid branch " BNE NOT0B" for all that follow 0B while they're still the same style? Also the branch is only a few bytes....

Code:

NOT0A        CMP #$0B                 BNE NOT0B                 LDA #<RY11                 STA WELKERY+1                 LDA #>RY11                 STA WELKERY+2                 JMP XROWREAD NOT0B           CMP #$0C                 BNE NOT0C                 LDA #<RY12                 STA WELKERY+1                 LDA #>RY12                 STA WELKERY+2                 JMP XROWREAD etc. All error from here on

Am I doing something wrong? Or is it a bug?

Hi! I've pm'd you with a dropbox link containing the entire project.

Mind it's an import of over 5 years old

Edit: I use Release Version 2.3.0

Perhaps there's an invalid invisible byte in the code, try copy and paste or opening it in another editor alternatively open in a hex editor and see if there are any extra bytes that are not supposed to be there.

Two issues that I would LOVE cleared up.

* The close/reopen - reformat code bug.
* A Commodore 64 font for the editor. I am getting SO confused between lower case l and 1 that I'm not seeing these bugs when recheck my code.
Any way of adding one? There aren't many fonts to choose from....

Thank you for your help and fixing the bug man!
I'll donate some moneys to you later so you can treat yourself to a beer of me

Nice work-around! I would have given that a shot if ajordison wouldn't have fixed the label bug for me It works now though so there's no real need for me to change the code anymore.

Nice to see different coding approaches though, I'll keep it in mind for any fututre projects or similar problems!

I'm trying to make a simple BASIC program with sprite data.

How do you generate a prg-file of the BASIC program so it will include the sprite data? I have exported my sprites to the memory but after I have compiled the prg file the memory is blank where the sprite data should be.

I'm guessing it only exports the code and makes the BASIC listing but how do I include the sprites?

My BASIC listing:
2049 ($0801) - 2655 ($0A5F)

My Sprite Data:
12288 ($3000) - 12800 ($3200)

I want it to make one file prg out of 2049 ($0801) - 12800 ($3200). How do I do this?

Thanks! I got it working by exporting all of my sprites with two bytes off and then following your instructions. But the solution doesn't really make sense to me. Why doesn't it work if I put the real start address f.e. $3000 ?

edit: nevermind. You explained already.

Well now that the football's nearly over, fill the void with a new version of CBM prg Studio.

Version 2.4.0 is ready to download at the link below. It's mostly a bug fix but there are new features for C16 and Plus/4 users. Don't worry C128 users, it's your turn next month with VDC support in the screen designer.

Enjoy!

As usual, many thanks to the feature requesters, bug hunters and donators who helped with this release!
_________________