Jump to content

jwierer

Members
  • Content Count

    949
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by jwierer

  1. I don't have 64-bit Vista to test, but I can try on Window 7 64-bit on Wed and see if it fails. Unfortunately that's an open source library that I can't really change so if it's an issue that is not something I can really change unless I find an alternate library to use. Sorry, Jeff
  2. 96 x 192 should work fine with the Bitmap Kernel, but it's not going to work with the standard kernel (maybe in the future though). I could have made this more integrated with vbB with warnings, but it was really written to be a standard alone .exe for use with the bitmap kernel. It's use assumes you're familiar with the limitations of bB and the bitmap kernel. -Keff
  3. Not sure how that one got in there. I can fix the settings tab, but I think the problem with the sound system not working is due to the fact that you're still running under virtualization? I can double check this works on 64-bit when I get back home, but I am pretty sure it's the virtual machine that is failing this for you. -Jeff
  4. At the bottom it always tells you your current line number and you can jump to a line number by pressing Control-G or Edit->Go To. -Jeff
  5. Would you expect that option to delete all temporary music files or just the most recent? Say you had the option disabled, tested some music, and then enabled that option. Would it clear all the files? -Jeff
  6. Not a bug. What I think you are seeing is you are trying to set either the Player or Playfield color equal to the background color. The background color is shared between the sprite and playfield designers and you can't have the same, let's call it a pixel color, equal to the background color. Check your player color it's probably already $00. Just noticed that as well. That's an artifact of me copying/pasting code and not changing the dialog title. That must have been like that for a LONG time. Will fix it. I'm glad you finally converted I can look into that. Thanks for the suggestion. -Jeff
  7. That's what I call the big playfield (or sprite for that matter) effect. As far as I can tell it's an issue of a datagrid control layered on a tab control bug. There is nothing I am doing to make it scroll, it just happens. I tried about 6 month ago to see if I could capture that occurance using win32 APIs but was ultimately unsuccessful in trying to force it to stop. To be specific, I couldn't stop it so I was trying to catch it and scroll it back, but that was just making it shake... I've learned to live with it or buy a bigger monitor. -Jeff That might address your problem, but it doesn't solve the main problem. At the point were the scroll bars appear it happens.
  8. That's what I call the big playfield (or sprite for that matter) effect. As far as I can tell it's an issue of a datagrid control layered on a tab control bug. There is nothing I am doing to make it scroll, it just happens. I tried about 6 month ago to see if I could capture that occurance using win32 APIs but was ultimately unsuccessful in trying to force it to stop. To be specific, I couldn't stop it so I was trying to catch it and scroll it back, but that was just making it shake... I've learned to live with it or buy a bigger monitor. -Jeff
  9. Does it happen to you in Builds 544 or 548? I can look at changes between those if they don't have the same problem. Also can you PM me the full error? Might give me a clue as to what is happening to you. -Jeff
  10. I'm using Vista - working fine for me? anything else in your code that would be special? -Jeff
  11. Using the same color for each ghost does introduce an interesting challenge as you don't know what AI is controlling the ghost. I like it. -Jeff
  12. I like it, though I suck at landing that thing. -Jeff
  13. Sure, I can make the tool strip compile button remember your last compile option. -Jeff
  14. Can you post what is in your visualbB folder? I still think you are missing a file. -Jeff Here is a snapshot of my directory. If it helps, I am running this in a virtualbox that is running windows XP. Not sure that would cause any issues, but I figured I would add it just in case. Everything else seems to work ok from it. Thanks. "I am running this in a virtualbox that is running windows XP" - I've never tested it under VirtualBox. I recommend copying your folder to a physical machine and see if it works. If so, I think you found your issue. -Jeff
  15. Can you post what is in your visualbB folder? I still think you are missing a file. -Jeff
  16. Great idea. I don't know why I didn't implement that before because it only took about 5 minutes to implement, though I don't have the fancy preview you see with Firefox. This will be in the next release. Thanks, Jeff Good to hear that. Also I found out that after the VbB found a Syntax error, it makes bold and red the font of that particular line of code with problem, but after I fix it and re-build the program (and works) still it is red & bold. Yeah unfortunately the syntax editor is not that sophisticated. Hitting <Enter> at the end of the line will force it to re-check the syntax of that line and if the error is gone it will reset the formatting back to normal. -Jeff
  17. Make sure you download BOTH zip files and extract them to the SAME folder. In a nutshell it can't find one of the required .dlls. -Jeff
  18. It appears some missing registry settings was causing the problem. For anybody that can't open a playfield, or sprite, unzip the attached file and double click it (vbb_fix.reg) to import it into the registry. That should do it. vbb_fix.zip -Jeff
  19. Not sure what you are looking at when you say this? I can confirm that vbB is working fine on Vista Enterprise 32-bit, because that's what I use on a daily basis. I am more inclined to think it's file permissions or A/V software putting a lock on the file or something non-Windows related. -Jeff Jeff, Right-click on the file in explorer and select properties. Example attached. I don't think it's the A/V...one I run the same software on another machine and two...I turned it off...completely. Same thing with the firewall. Permissions, I could see. My account is administrator and the owner is administrators. I tried taking ownership, but that didn't seem to make a difference. What specifically is going on in the double-click action? Maybe I can whip up something that does something similar and see if I can generate some debug messages? Oh ok the properties on the .pla. Yes that is exactly what I have. I'll PM you a debug version later today. Perhaps we can nail down the function that is failing you. Happens with Sprites I assume as well? -Jeff
  20. Not sure what you are looking at when you say this? I can confirm that vbB is working fine on Vista Enterprise 32-bit, because that's what I use on a daily basis. I am more inclined to think it's file permissions or A/V software putting a lock on the file or something non-Windows related. -Jeff
  21. Great idea. I don't know why I didn't implement that before because it only took about 5 minutes to implement, though I don't have the fancy preview you see with Firefox. This will be in the next release. Thanks, Jeff
  22. Well, I just had updated from the RanomTerrain update, but I tried out with the original batari 1.0 and still is not working. I just upload the bas source code I'm trying to compile if someone else can do it, so there I can see I have something with my configuraton. thanks in advance. Devwebcl Thanks for posting the source. The good news is your compiler is working normally because the problem is that the playfield is too large for a normal bB playfield. If you want a larger than supported playfield you'll need to generate the assembly option in imgToCode and use the bitmap kernel. -Jeff
  23. He was using Media Edition of Windows so I assumed it was something isolated to that. What are your exact steps because I also have 32-bit Vista and can't replicate the problem even if I use the same directories you're using. Are you logged in as a local admin? If you wait for a few minutes does it work? I wonder if you have some A/V tools holding open the file which is having an effect? -Jeff
  24. Are you using the Windows 64-bit compiler found in this thread? I've encountered a couple different situations where code would not compile with that version. I just use a 32-bit machine and the older compiler until it's resolved. -Jeff
  25. A mini-graphics editor? You over estimate my graphics skills I think I came up with a good alternative though. I'll send you a PM later that you can test out. -Jeff
×
×
  • Create New...