Recent posts

[is]

#11

Stunts Reverse Engineering / Re: Restunts repository - Git ...

Last post by Matei - Yesterday at 11:40:20 PM

It may seem so because we now see everyday programs taking up hundreds or megabytes or gigabytes,

Try my game:

https://matei.one/idxscr.html#download

Besides, if you only need to load a PNG file and then save it, you depend on code that can also process compressed audio, for example. It's like carrying the computer with your program.

Not with my functions, which draw graphics and save BMP files only with the standard C library. I didn't need to read BMP files until now though, but I could do that.

Which brings me to this. If you send somebody a letter in a random language

That's the C language, it's not random, and "somebody" is the hardware to which you send it, which also has who knows what drivers and other programs on it.

and you accompany it with a guy who speaks a hundred languages including it,

That's SDL and it will translate your letter to anyone to whom you sent it. The idea is that you don't know who you send it to, but SDL will translate it to anyone. No DOS though.

https://matei.one/idxchess.html

but the version for DOS/DOSBox, which is available below, uses some graphical functions available with Open Watcom, as SDL has no support for DOS.

But SDL not only does this, it also doesn't even provide the translator guy:

As mentioned, SDL is the translator.

#12

Stunts Related Programs / Re: SDL 3

Last post by Duplode - Yesterday at 11:35:14 PM

Good catch; I wonder if my environment is somehow interfering with the window size (will try to find out later).

Yes, it is my environment. I normally use XMonad (a tiling window manager) on this computer; switching to a Xfce session I get no segfaults, and the expected 800x600 size is reported. Maybe the two pixels taken by the window borders are somehow being deduced from the available window size (but if so, why just from the width and not the height?). It's mostly academical now, but if I find a workaround for XMonad (and I guess there must be one) I'll post it here.

#13

Chat - Misc / Re: Association game

Last post by CTG - Yesterday at 11:22:30 PM

mustard

#14

Competition 2025 / Re: Semi-Retirement Announceme...

Last post by CTG - Yesterday at 11:21:23 PM

How could I miss this one?

Have fun in private life, Helmuth!

#15

Stunts Related Programs / Re: SDL 3

Last post by Matei - Yesterday at 11:16:12 PM

You can also try with various resolutions (file "config") and see what happens. Is the resolution set in "config" ever reported properly?

#16

Chat - Misc / Re: Association game

Last post by Cas - Yesterday at 11:14:34 PM

Sausage

#17

Stunts Reverse Engineering / Re: Restunts repository - Git ...

Last post by Cas - Yesterday at 11:13:40 PM

as soon as you would try to write a multi-platform wrapper (capable as SDL2-3) around input,output,sound,etc. you would see that the SDL api is really small for what its helping/keeping from you - you're just not used to it - thats all

It may seem so because we now see everyday programs taking up hundreds or megabytes or gigabytes, but really, it's huge. Take the most complicated game from the 90s, strip out data (animations, graphics, audio) and you'll see the code is rarely more than a megabyte. SDL is a layer on top of a layer, on top of a layer and so on. The degree of dependency and lack of knowledge of how the code works is extremely high. No person that worked on it understands all the code and nobody making programs for it does either. Besides, if you only need to load a PNG file and then save it, you depend on code that can also process compressed audio, for example. It's like carrying the computer with your program.

Yes it does. All you have to do is make your graphical and sound functions work with all 3 versions of SDL, which is what I did.

Which brings me to this. If you send somebody a letter in a random language and you accompany it with a guy who speaks a hundred languages including it, you could say the letter is written in a lingua franca, but that's not true. It's the translator that makes it seem so. And of course, you can send the letter in an envelope, while carrying the guy overseas may require a seat on a plane or a room in a ship. But SDL not only does this, it also doesn't even provide the translator guy: it just tells you that translator exists and you have to find it and bring it home yourself, ha, ha.

---
I realise all this may not matter to many people. Some of us may be very picky with their food, but can sleep anywhere, while others can eat rubbish, but then need a comfy mattress. I like clean, logical, comprehensive code... I don't like using black boxes. I feel the need to have full control and know what I'm doing. Not having that is uncomfortable to me and even very boring, because seeing the inside mechanisms of things is what has attracted me to many things I'm passionate about, including programming.

#18

Stunts Related Programs / Re: SDL 3

Last post by Duplode - Yesterday at 11:04:39 PM

Good catch; I wonder if my environment is somehow interfering with the window size (will try to find out later). Trying with the 6.2.0 from your site, both the SDL3 build and full screen always segfaults. The provided binary (which is the SDL2 one, I believe) segfaults some of the time (if I retry enough times it works somehow), and the size reported on the console for it is 798x600x32.

#19

Competition 2025 / Re: Cloned replays, ZCT285 to ...

Last post by Cas - Yesterday at 10:41:47 PM

Oh, it's really sad to read this   I don't see how this could have been accidental. I have planned a system to detect this automatically in R4K since a long time ago, but it never seemed necessary. I guess I'll have to find the time to do it and in the meantime, put attention to coming replays.

#20

Stunts Related Programs / Re: SDL 3

Last post by Matei - Yesterday at 07:24:30 PM

I think I found the problem. When you started the program, it said "1064x600x24", but 1064 means a width of 798 pixels, although it was set to 800. On my computer it says "1066x600x24". The SDL function to create the window is called in file graphics/forsdl3/graph2d.c at line 139:

Code Select Expand

SDL_CreateWindow(title,width,height,0);
The graphical functions then use variables RGLOB_width and RGLOB_height set equal to width and height, but the created window is smaller, so memory for those pixels isn't available, so "Segmentation fault". I don't know how to find the parameters of the window:

https://wiki.libsdl.org/SDL3/SDL_GetWindowSurface

Doesn't say. I can set RGLOB_width and RGLOB_height to smaller values than width and height after creating the window, but this is not reliable. Does the problem occur in the same conditions if the image is set to full screen ("fullscr=1" in file "config") or with SDL 2?