|
Post by Tom Mulgrew on Aug 26, 2005 20:22:12 GMT -5
Version 2.3.2 is out. This should fix the "Disk File" bug in standalone exes. I've also made a few changes towards making the language more like standard BASIC. Some of these changes are automatically available, like the new "Input" command (to replace the previous Input$() function). Some things you need to explicitly enable by switching to "traditional BASIC mode". (You do this by putting "language traditional" at the top of your program.) This includes such things as the "print" command automatically adding a new line (unless it ends with a . (It was setup this way so that existing Basic4GL programs should still compile and run correctly, because by default: print "Hello" doesn't add a new line in previous versions of Basic4GL.) It also has some other basic differences, such as no brackets on commands that don't return a value. language traditional dim a# TextMode TEXT_OVERLAID cls locate 15, 12: print "A triangle"; while true glClear GL_DEPTH_BUFFER_BIT or GL_COLOR_BUFFER_BIT glLoadIdentity glTranslatef 0, 0, -3 glRotatef a#, 0, 0, 1 glBegin GL_TRIANGLES glColor3f 1, 0, 0: glVertex2f 0, 1 glColor3f 0, 1, 0: glVertex2f 1, -.5 glColor3f 0, 0, 1: glVertex2f -1, -.5 glEnd DrawText SwapBuffers a# = a# + 1 wend And finally theres a mode which is like standard Basic4GL syntax, except with a traditional "print" command (which can be enabled by putting "language traditional_print" at the start of your program). -Tom
|
|
|
Post by STT on Aug 27, 2005 7:38:45 GMT -5
Good work, but there is still an error in compiled EXEs. A message comes up saying "ThingyQuest.exe has encountered a problem and needs to close. We are sorry for the inconvenience." (ThingyQuest.exe being the program I'm trying to compile.) If it is any help I can send the error report file
|
|
|
Post by Tom Mulgrew on Aug 27, 2005 17:58:30 GMT -5
Good work, but there is still an error in compiled EXEs. A message comes up saying "ThingyQuest.exe has encountered a problem and needs to close. We are sorry for the inconvenience." (ThingyQuest.exe being the program I'm trying to compile.) If it is any help I can send the error report file I might be able to make something of it. The actual error message looks like a generic Windows "this application has crashed" message. However the error report may have a program offset that I can use to figure out where in the program it went wrong (and hopefully give some clues as to why). Btw, does the crash happen immediately, or does the program run for a little while first? -Tom
|
|
|
Post by Tom Mulgrew on Aug 28, 2005 18:31:45 GMT -5
I've just found a nasty bug that crashes standalone exes when they try to load a non-standard sized texture that includes transparency (e.g. a png file with an alpha channel).
The error message sounds very similar to the one you're experiencing.
I've fixed it in v2.3.3 which I'll upload very soon.
-Tom
|
|
|
Post by STT on Aug 29, 2005 1:44:47 GMT -5
Okay, thanks mate.
No, the crash does not happen immediately, just somewhere between an inital "ThingyQuest V0.0.6 - Press any key to continue" screen, and the beginning of the main loop. Between which is sections where dimmings, structurings, textures, display lists and sprites are aranged in that order.
It is probably the texture bug. I use quite a few of non - standard sized textures with alpha channels, all of which are PNGs.
|
|