[SOLVED] Program starts, but separate window to run it in doesn't
appear anymore
lazarus / 9-Editor

----------------------------------------------------------------------
Wings2018 · 2025-09-24 11:22

Hello,

Since several days I started using Lazarus v4.2 / FPC v3.2.2 win64 and
compiled a program without problems.

It means, when I start my program from within the debugger in Lazarus,
normally a second black colored screen is opened and the program (with
its user in- and outputs) runs without a problem in that screen.

I believe I must have changed whatever parameter in Lazarus, because
when I start my program now the second black colored window doesn't
appear anymore, but the program is still running (I know it is running
because a logging file which I add to all of my programs is nicely
being updated continiously with expected data).

I tried a second program with the same negative result; even when
installing Lazarus on another laptop both programs show the same
behavior: no second black screen.

Can somebody give me a hint on what I might have done wrong? Does
somebody know if Lazarus has the option to dump each and every menu-
setting to a text-file for comparison purposes?

----------------------------------------------------------------------
dseligo · 2025-09-24 12:13

Look at the menu option Project, Project Options, Config and Target,
'Win32 gui application (-WG)'.

If it's checked, uncheck it.

----------------------------------------------------------------------
Thaddy · 2025-09-24 13:04

Note that this only goes for Windows and, contrary to the option
display "win32", also for win64: the latter is a bug in Lazarus.
(Only a display bug, but can irritate some people and should be fixed
after all these years, isn't it reported yet?).

----------------------------------------------------------------------
Wings2018 · 2025-09-24 14:46

Thanks dseligo and scoops (via private message), you both provided the
same answer and it indeed solves my problem by un-ticking the -WG
option.

Thaddy's remark about win32 being shown, but also being valid for
win64 and on Windows only is an important and helpfull addition, and I
think it can be added with little effort to the menu option (or via a
ballon). Let me try to raise a minor bug on this.

Meanwhile I'm closing this thread, thanks everybody, never before a
topic I raised was solved so quickly!

----------------------------------------------------------------------
n7800 · 2025-09-24 19:23

For information, here is a link to the issue on the bug tracker.