haha... cool!! :D
i like to see simple hand made textures turn into something totally sleek ^.^

i agree, especially with the screen drawing/trigonometry stuff :)

pete5990 wrote:How do I make the TIMER command as accurate as possible? It rounds to the nearest integer.

ex. a = TIMER

just use a double to store the value.. :)

try this: #INCLUDE ONCE "zlib.bi" #undef uInt #undef uLong #undef Bytef #undef charf #undef intf #undef uIntf #undef uLongf #undef voidpc #undef voidpf #undef voidp #INCLUDE ONCE "WINDOWS.BI" #INCLUDE ONCE "DialogFunctions.bi" #INCLUDE ONCE "vbcompat.bi"

Antoni wrote:Well, an optimizer compiler helps too, once you got the best algorithm.

I hope FB 0.16 (GCC frontend) will allow an -o3 optimization and beat the crap out of all of them :D

can't wait to unroll those loops lol

Anyone except me who doesn't manage to compile with the "static" lib? Anyone that could bother to fix the DCC-stuff? Would be really useful. Thanks anyways voodoo. Will be using this one frequently I suspect. you're welcome.. and sorry about that lil mistake.. :) works OK here, but maybe the recent...

Antoni wrote:Hey, my sieve program ran without format problems, at last!
Freebasic is considered 5.7 times better than C at this particular task. As victor said, as long as no one implements my algo in C.

http://shootout.alioth.debian.org/gp4/b ... ang=FreeBASIC

good job mate :D

Dr_D wrote:Where the hell did you guys get an insight installer? The only one I can find freezes my pc. I need it too! :(

just install cygwin.. and select the package ;)

Sisophon2001 wrote:

Thrawn89 wrote:<snip>
I dont even know how to use gdb, tryied it once...failed

Thrawn

Try Insight. It is easy to use, and worth while learning.

Garvan

Indeed :)

i remember i had this issue with Pload before.. and i tried to debug it, but i gave up.. probably caused by the globals/shared variables.. leading to unexpected results.. if so, try adding code to clear everything before loading a new png, or just move everything into context based subs/functions.. ...

nVIDIA GeForce FX 5200 :)

v1ctor wrote:That's compatible with QB, STR() won't add a blank before a positive number, but PRINT will.

In Linux the pad (,) in PRINT is aligning at the wrong column, i'll check that later.

i never knew that QB did that :-)

Antoni wrote:What I complained about was that strange spureos space that happens only in Linux...why?

not only linux though..



produces extra space on second line.. same weird error..

<< fb .15b on windows xp sp2

ooh sorry i meant chr(34) :D
just woke up and apparently i wasnt really concentrating yesterday :)

chr(34) = "

:-)

you should replace the rest too items = g_list_append (items, @"First Item") items = g_list_append (items, @"Second Item") items = g_list_append (items, @"Third Item") items = g_list_append (items, @"Fourth Item") items = g_list...