Program runs fine in Debug mode but not without?
Blitz3D Forums/Blitz3D Beginners Area/Program runs fine in Debug mode but not without?
| ||
| I'm sure this topic has had the arse kicked out it but I can't seem to find anything on the subject in the forums. All the sounds and graphics files are definately in the same directory. I get a memory access violation but nothing with debug on so I've no idea what the problem could be - any suggestions?? I recently added mouse control (movemouse, mousedown & mousespeed ) into the program which seems to be the only difference to a previous version which works fine. Cheers |
| ||
| Are you running full-screen in debug mode as well as non-debug, or just in a window? |
| ||
| I'm running fullscreen in both modes. Is this the problem? |
| ||
| If anyones interested I pinpointed it to the mouse commands. It seems that using the MoveMouse command before the Mousedown commands causes the problem .. I'm not convinced that this was the problem though. Is it possible that when I click on 'Run Program' on the menu, and the mousepointer x position on the desktop (1280,1024) is outwith the graphics window width (640,480) , MouseXSpeed() has problems with. i.e. I have to movemouse to a point within the window before I use the commands? Anyhoo, I'm waffling now ... jx# = (MouseXSpeed()/7.0) jz# = (MouseYSpeed()/7.0) thrust = MouseDown(1) shoot = MouseDown(2) MoveMouse 320,240 |
| ||
| I had a similar problem at one time. it was caused because I called mousemove() before actually doing the graphics() commmand! that caused the exact same issue |
| ||
| This is the thing that gets to me with BBPlus, and the reason I might change languages. If something happens out of the ordinay we should have to go, humm, ok so I CAN'T do that, without actually getting any real explanation for why you CAN'T do that. And why the hell arn't types/fields not global?, C'Mon people sort it out etc... Ok *calms down* but I hope you know what I'm getting at, if something doesn't work in BBPlus and you can't see in the code why it's not working, or you do something in BBPlus and it works, but why does it work?, no one seems to know. This is getting me very frustrated. I can't seem to code in a language that just has things that work and don't work without any real explantation. Ok, I've said my 2 cents hope you experts can put me in my place. |
| ||
| @Jono You are not alone with your opinion. Although I am still new with Blitz I feel the same. The documentation is not sufficient, commands are not very error-trapping-friendly, sometime things work, sometimes not. without any proper reason. And the built-in IDE is crap at detecting syntex errors ... |
| ||
| It says in the programe under command preference "Click for replys to this command". But when I do I always get a 404 error (page not found) which is very frustrating when you want to find out more information about a certain command your trying to get working, and maybe if the people here making the software could set that up then I could know why certain commands do what they do. The IDE does need alot of work it would be really nice if I could chose what colours it uses for highlight and what colours it uses for bits and pieces but oh well. |
| ||
| Hey, i agree that the commands aren't very well documented, but the forums are always here, and i don't think anytime i've had a problem, the forums haven't been able to solve it. Keep the faith! |
| ||
| @Ross C Yes, the forum is here. thank god. But there is NO EXCUSE not to properly document a commandset in a programming language!! |
| ||
| I agree that Mark could update the documentation to perfect shape in a single weekend if he wanted to. Just build on what's there and fill in the holes. It's not THAT hard. |
| ||
| ;- |
| ||
| @Kournikov You are correct. I also spend hours upon hours reading forum threads to find solutions to the simplest problems, which could be avoided if the command-set was properly documented in the first place. |
   |