java.net.UnknownHostException: freebasic.net A failure to resolve freebasic.net sounds like a DNS issue. It suggests the build server couldn't reach its DNS provider. So either the DNS provider had an outage, or the Internet connection went down. If you can configure the DNS server, Cloudflare (1.1...

You could try partitioning the points into a grid of N*N cells. Then you’d only have to check the points in each cell against points in the same cell and neighbouring cells. Note, depending on the distribution of points, you might find that most points are clustered together in the same cell. In tha...

You could try the suggestions in viewtopic.php?p=174567#p174567, which explain how to compile your own ffi, or to disable it in FB.

I agree with Put #, but: open "blabla.txt" for output as #1 print #1, "AB"; close #1 Gives a 2-byte file here, and (without the semicolon): open "blabla.txt" for output as #1 print #1, "AB" close #1 A 3-byte file here. Last one 0x0A (LF). Probably 4 bytes on ...

You may be better off using Put # instead of Print.
Print is designed for text, and it may not always work properly with binary data.
If you want to omit the newline after Print, you can put a semicolon at the end of the line.

So we’re talking roughly a billion lines of text? ... A good strategy might be to sort the array, then duplicate checking is easy. Have you ever tried to sort a billion lines of text? Any idea how much time it will take? OK, fair enough.. Running the numbers, I guess a terabyte file of a billion li...

So we’re talking roughly a billion lines of text? One question that occurs to me is, how many unique lines are there likely to be? I think any hash-based method will need a table with at least that many entries, which could easily be gigabytes in size and might not easily fit in memory. And I’m not ...

In general it's hard for #include/pragma once to detect when the same file is accessed multiple times through different paths, so it's worth combining it with something like #ifndef ... #define ... #endif. C/C++ have a similar problem: https://en.wikipedia.org/wiki/Pragma_once#Caveats I guess the id...

Even if FB did support label pointers, it would still be a hassle to get them working with Restore, because labels aren't treated as code pointers with Data/Restore.. Data may not be the best method nowadays, but I guess something like this would work: #macro datalabel(l) l: sub restore_##l() restor...

I've added the ability to set delays now, e.g. using .addDelay(10) for a 0.1sec delay (i.e. using the native "centisecond" unit). I've wondered whether I should have some sort of function for adding "realtime" delays, which would allow videos to run at the same speed they were re...

Yeah, frame delays would be useful, I hope to look into that.
Looks like giflib has support for that, although it looks a little more convoluted than I hoped. (That’s been my experience with most things in GIF/giflib so far..)

I can't test on Windows at the moment, but it's a good sign if gifwriter.bas compiles and links by itself.
What command line are you using? You either need to compile them both at the same time, or compile gifwriter.bas to a library and link example2.bas to that.

EDIT: glad you got it sorted!

Those functions aren't from giflib, but are class methods implemented in gifwriter.bas. Are you compiling the example together with the class module?

PS. I'm using Linux, libgif7 version 5.1.4-2ubuntu0.1 amdb64.
__GIFLIB_VER__ is the default, i.e. 5. It probably wouldn't be hard to adapt it to 4.

I wanted to be able to record little GIF movies from FB graphics programs, but I was finding giflib a pain to work with, and not finding many good usage examples.. Then I found apparently it doesn't seem to do any attempt at frame size optimisation, which isn't ideal when outputting lots of similar ...

Hi Mysoft, I'm glad that you found the headers posted here useful enough to adapt to your needs. Any improvements or contributions you want to make to the code are welcomed, and other people here may perhaps find them useful. But I'm sorry - we don't want that kind of abusive language or unconstruct...