I've tested the example program. It created the hardware fullscreen on non-primary monitor No. 1. The console window was created on primary monitor No. 2.
Attached is an allegro.log debug level.

Granted, but the egg is thrown at you and hits you in the face, so you literally have egg on your face.

I wish I had more consistent aim in Fortnite Blitz Royale.

Quote from: jkapp76 on April 21, 2024, 11:15:30 PMhttps://u.pcloud.link/publink/show?code=XZdSoOVZSpJ2pulFthS12h1B1k3PCB964IDV

Here's a link to Lemmings 3 for Windows.

Just unzip to a folder and run the .Bat file.

my laptop almost exploded

it really really stinked bad.

granted! however your productivity drains all your autonomy turning you into a flesh robot

i wish for something simple, a singular egg, NOT MULTIPLE, DONT GET ANY IDEAS. YOU HEARD ME? ONE EGG.

i added calculator image but i forgor how paste image

not dead yet! sorry namida,    also the alpha was a better pfp i liked that one

I'll focus on the hardware fullscreen monitor choice.

• In Windows, configure your monitors such that monitor 2 is the primary monitor.
  
• Download this example program: prim-moni-hw.
  
• Put it into a Lix directory. (Or into any other directory where you have Allegro 5.2 DLLs.)
  
• Run it. (It will run for 4-5 seconds, then self-close.)
  

On which monitor did it create its hardware fullscreen display? On the primary monitor 2 or on the nonprimary monitor 1?

Source code

My source code for prim-moni-hw, both in D and in C++. The above download is from the D version. For asking the Allegro 5 devs or for filing a bug, I'll have the C++ source.

The idea is: The simplest-possible code to request a hardware fullscreen display from Allegro 5 is the following. In an ideal world, it should heed your primary monitor configuration on Windows. But I expect it to ignore your configuration and pick the unwanted monitor 1.

Code Select Expand

al_set_new_display_flags(
    (al_get_new_display_flags() | ALLEGRO_FULLSCREEN)
    & ~ALLEGRO_WINDOWED
    & ~ALLEGRO_FULLSCREEN_WINDOW);
auto display = al_create_display(640, 480);

-- Simon

Quote from: GigaLem on August 02, 2025, 12:24:59 AMmy suggestion would be the freedom of changing the RGB value at will with the default being the fuchsia it is.
The other part of the suggest would be Trigger area opacity or brightness, choosing how much of it to be opaque

Right, but let's not lose sight of what the program is: it's a lemmings engine, not an image editor. We'd be better off keeping the options as simple as possible rather than making the user spend too much time in menus.

Quote from: GigaLem on August 02, 2025, 12:29:17 AMLook at a screenshot of Windows 95 lemmings and compare it to Mac Lemmings, the graphics are very different, recognizable but one is more "hi def" than the other.

The resolution is the same, and on a technical level, I get the feeling the capabilities are the same (or at least close) - but it does feel like the Mac version had less effort put into it. The Win95 one looks like an actual effort to remake the graphics in higher resolution and color depth, whereas the Mac one just looks like a fairly decent upscaling (aside from the skill panel, which is actually quite nice, especially compared to the Win95 one).