| Re: [AD] allegro_message under X |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] allegro_message under X
- From: Evert Glebbeek <evertg@xxxxxxxxxx>
- Date: Wed, 27 Oct 2004 10:15:55 +0200
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=dUOrljUpDJPlPxQcyQgtoi6J88vFkXKF8ysDGNpKM0/Lt8WAHMTP1h5bJ/gFg+dblMNWLd628Vx2r131kBhDs9vHSDtd767nrkpcoxj7McPYH2VoGItowONLYNanzbZggoMMIdlORmAUWD48HpgniGt/dqqlpifhPISOiqQyK+k=
> I for one think, calling xmessage is not a problem. I already like how
> the Allegro example popup all those windows now - even exfixed works
> fine. And we have the same behavior now in windows and X11 - so I'd
> see no problem just applying the patch (along with the one to hide the
> window with GFX_TEXT).
Personally, I think allegro_message() should write to the stderr
stream, although I realize that this is a problem if stderr is not
visible (as an aside, is anyone else annoyed by KDE applications
printing warnings and error messages to the terminal while they are
running?).
I would prefer to keep the current behavior personally, so I'm going
to provide the all-mighty compromise: can we make it a configure
option?
Evert