Re: Problems with the "mwindows" switch

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Sat, 23 May 2015 00:20:57 -0700 (PDT), NiGHTS wrote:

> The problem is that the program will not start when the "mwindows" linker
> option is used. I don't know how to go about debugging this problem.

It quite difficult to imagine how mwindows could have anything to do with
that.

"Will not start" means what, technically? Any properly linked executable
will start, otherwise Windows gives a message box that the executable is
corrupted etc. Thus, again, what is the problem? No window? No process?

There are three vital stages of a GTK program execution before it becomes
operational and anything visible happens:

1. Elaboration phase includes initialization of static objects and
sections, loading and linking to dynamic libraries etc.

2. Execution prior to entering the main messages loop.

3. Creation of GTK objects, like the main Window, within the messages loop.

(Note that during #1 no Text_IO could ever help)

P.S. GTK is not task/thread-safe. Any GTK (GDK, Glib, Gobject etc) calls
shall be done on the context of the main task, the one running the messages
loop.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de