delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/06/08/15:50:09

From: Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro GUI Woes :(
Date: Sun, 8 Jun 1997 19:50:26 +0100
Organization: None
Distribution: world
Message-ID: <laHqS6Ay7vmzEwRb@talula.demon.co.uk>
References: <5neqr9$s0f AT news DOT interlog DOT com>
NNTP-Posting-Host: talula.demon.co.uk
MIME-Version: 1.0
Lines: 20
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Gautam N. Lad writes:
>The problem is the do_dialog(), when called, expects something to 
>occur, and the the function is exited.  I don't want that.  I expect 
>the program to allow editing, if the user is over the grid, but if the 
>user goes in the GUI objects area, the do_dialogs() is called.

There are two ways you could do that. If you get the work-in-progress
Allegro version from my webpage, you can call init_dialog(),
update_dialog(), and shutdown_dialog() from your own code rather than
just transferring control entirely to the do_dialog() routine, so you
can mix the Allegro GUI processing with other code of your own.

Alternatively you could implement your grid as a custom GUI object, in
which case the do_dialog() routine will send you messages whenever the
mouse moves on top of your grid object...


--
Shawn Hargreaves - shawn AT talula DOT demon DOT co DOT uk - http://www.talula.demon.co.uk/
Beauty is a French phonetic corruption of a short cloth neck ornament.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019