jwierer

The good news is you can fix this yourself. Right now it defaults to loading the manual.html stored in <bb folder>\manual\. Save this link locally from RT's site. If you delete that file it will try to go grab the online copy. I should probably default to the online copy and use the local copy if the internet is not available... It's a good idea, but right now once you convert to text there is no way to go back to generating the assembly. I'll have to look at the code it might be easier for me to import binary and generate the assembly equivalent. -Jeff

You should be able to grab the latest from this thread but as you'll see at the end there are other issues using it. -Jeff

Good catch, though I'm suprised it ever warned at all? The only code I see is a warning if the project root was selected, unless I deleted something. Fixed in the next release for sure. Thanks! Jeff

Looks like you figured it out, but in the future if you create a sprite you can actually right click "Preview in Emulator" and it will generate the code for a bin where you can move it around screen. Works the same for Playfields. -Jeff

I don't know if Michael ever got the bitmap kernel working beyond the displaying a single image phase. Perhaps you're use can motivate him to continue to develop it You might want to bump that thread to recapture attention to the work. My tool will output the necessary format for his current work and I'd be happy to update it if he needs changes. -Jeff

That would probably happen if you deleted ImgtoCode.exe? Is it in the same directory as visualbb.exe? It was built as a standalone executable so you can just double click ImgToCode and it will load. It will import an image, any type, and either output a single sprite or playfield frame or a set of animated frames. You can create a hires screen as it was originally written to work with the bitmap kernel. -Jeff

I know about the simple things! I'm on call this weekend, and I just got paged for somthing even more mindless, that 3 people missed and paged me on. I should probably have it warn you if you have unsaved changes before compiling. The next update will include that. For what it's worth, if you go to the settings tab there is an option to always save unsaved changes before compiling. -Jeff

LOL! Miracle of miracles, what a difference! I guess that makes sense since it is passing the code to another parser... THANKS A BUNCH! Now I can get started on my ideas, and then the hopefully less obvious questions will come! It's usually the small things Happy coding! -Jeff

Are you saving after you copy and paste the code into the editor because that is what happens when you compile a blank piece of code. -Jeff

Looks like his site was hacked, but the videos are still here.

Luckily I still have a 32-bit Vista machine that I can use with the older compiler, but I wanted to move this over to my newer 64-bit Windows 7 laptop. Hopefully batari will see this thread is active again and take a 2nd look. Seems like a common code bug because it happens in the java-based compiler as well. -Jeff

What I would really like is to have a better way to detect and automatically correct syntax errors, but for that I would have to understand the language a whole lot better. What I could imagine adding is a set of inline assembly blocks and common mini-kernels so that less experienced programmers could use them. -Jeff

Absolutely. I am not sure why I never did that myself. If anybody has a good starter project for music DATA instead of SDATA, it should not be that hard to add in the future. -Jeff

The link is working for me?

I've come across situations where this compiler doesn't work. For example if I try to compile the attached file with the original compiler it works, but if I use this update I get the following error. DASM V2.20.07, Macro Assembler (C)1988-2003 bytes of ROM space left in bank 1 bytes of ROM space left in bank 2 1469 bytes of ROM space left in bank 1 2386 bytes of ROM space left in bank 2 1469 bytes of ROM space left in bank 1 2386 bytes of ROM space left in bank 2 --- Unresolved Symbol List pfwidth 0000 ???? (R ) Fatal assembly error: Source is not resolvable. Errors were encountered during assembly. I've tried it with your java-based compiler as well with the same result so it seems to be something in your newer source. Here is the .bas source and the resulting .asm files if it helps debug. Horse.bas Horse_ASM.zip *Update* this updated Kernel fixed it for me. -Jeff

Thanks!

Added a new build today which is just a few bug fixes a new tool for music and sound editing (see screen shot). You can download from the first post. Because AA limits 2MB uploads you'll need to download both files and unzip it to the same folder. New Features New Music and Sound Editor Fixed Bugs Error loading when using a non-US English version of Windows Image converter would generate incorrect code when converting animated gifs to .bas code Trying to add a new item to the project explorer before selecting a project would crash vbB known Issues Periodically warning messages not be cleared, locations will be off, or are just plain Wrong. You can hit Refresh, or F5, to force a full check of an open code file should clean it up. -Jeff

If you get an error, that vbB detects, it will tell you the line number and you can right-click, jump to error. Also as you move around it tells you your line/column location in the status bar at the bottom of the application. -Jeff

If it's not compiling then it might be your bB configuration. I would double check you didn't delete any files there first. -Jeff

No. I am not confusing anything. I was just mentioning that stupidity of not allowing the user to decide where to install it (forcing it always to c:\Atari2600, which is pretty friggin' stupid and underestimating the user's intelligence and capacity to use the computer - at least give us a CHOICE, doggone it!) while explaining the problem I have. VisualbB doesn't have an installer and doesn't require being installed to c:\atari2600. I would know, I wrote it. Now somebody probably did create their own installer and probably shared it with the rest of the world to make life a little easier. I haven't tried it, so I cannot comment, but calling something stupid is not very gratifying to the authors that develop software for free and share it with individuals like yourself. A little tact might go a long way in getting somebody to help you. -Jeff

I have this exact same problem. I can't get anything to show, except a blank playfield - that works just fine. Whenever I draw something into it, and then SAVE and then replace the blank playfield with the one I drew something on - - - "Missing Binary - Could not locate default.bas.bin and could not recompile. Please check to make sure it was compiled correctly." I also tried all those update things etc... no change. I am using Windows XP, I think SP2 or 3. I tried to do everything they suggest in the tutorial video in youtube, but when he says 'you should see the playfield pop up..', I just get that error. Oh btw, I really hate the installer; it forces you (in these modern days!) to install into C:\Atari2600! I mean what's up with not asking the user WHERE he would like the program to install itself? Sheesh.. not everyone is a bumbling mainstream idiot who doesn't know where he wants to keep his files, and especially considering it's a 1) Programming language 2) for a very OLD computing technology you could really understand, how people who are interested in this one, have used computers since the 80's, perhaps even since the 70's, and learned those good habits from those eras to actually arrange things as THEY see fit, not as bill gates sees fit. (I hate the whole windows registry thing and how every damn program wants to install into c:\ and all those stupid config-paths in Windows dir - who decided that PROGDIR: isn't good enough anymore for configs and such? Sheesh!) Sorry for ranting a bit, but damn.. - Monk Sounds like you're confusing multiple things. Visual bB assumes you already have installed bB correctly. Drawing a playfield is one thing, but you actually have to place the playfield code into a basic file and compile it. The fact that compilation fails is probably because you never installed bB correctly. I recommend you try walking through the bB compiler setup and confirm that is working first. -Jeff

People born after 1965 are interlopers. They must be dealt with swiftly and harshly. 1965? Move that to 1975 and I am in agreement

What's the modified date of 2600basic.exe? Wednesday, ‎February ‎14, ‎2007. That's the original release if I recall? I'll have to try on a different machine. Might be a bug... -Jeff

What's the modified date of 2600basic.exe?

Thanks! What version of the bB compiler are you using? I moved to this one because I now have Windows 7 64-bit and this code crashes the compiler. I haven't found anything else that does this? -Jeff