| Re: [AD] Overloading Alert |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Overloading Alert
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Sun, 23 Jan 2005 13:50:29 -0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=N3gVusIG1EaB+BQkVG/ZaBtXeZgVVCkvV0uzoux8MFRGb4uBlU2fRvkysRaL2Us6Wjv9AO0Ro+Stw3PO8utPjjsOHsKfb2qCXcSj/zQXRU+PpniN9YE8QObGDSDRoarUn1RjucmG1Ky5HN2DrLJhu57S3vGLslOl/mVZkf6qCnU=
Evert Glebbeek wrote:
I think we should have a popup_message(char *s, ...) and possibly a string
for the button text and leave alert as it is.
Hmm.. perhaps we could modify allegro_message to use a popup GUI dialog
when in a gfx mode? The current implementation of allegro_message says
it should not be used when in a gfx mode, so extending it to use the GUI
in a gfx mode doesn't sound ilke it'll break anything. The only issue
would be no clean way to change the button text, though with clever use
of a special char sequence, that could be fixed. Like:
allegro_message("This is a message box\nPh34r"
"<\some-special-escape-sequence>Click Me!");
The escape sequence could even have a special define to clean that up:
#define BUTTON_TEXT "\some-special-escape-sequence"
allegro_message("This is a message box\nPh34r" BUTTON_TEXT "Click Me!");
Not only that, but the Win32/xmessage/etc messagebox dialogs could even
be extended to use the special button text too.