| Re: [AD] Old patches return |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
> It indeed seems to be that way, and I certainly call object_message
> on some objects (which I think is appropriate, is it ?)
Yes, I think it is.
> Anyway, feel free to let it out if you think it's better that way.
The attached patch is the only part I'm ready to commit, but I'm not
convinced the change is really worthwhile.
--
Eric Botcazou
--- /home/eric/cvs/allegro/src/gui.c Mon Jun 16 14:45:02 2003
+++ allegro/src/gui.c Thu Oct 16 10:52:19 2003
@@ -361,7 +361,7 @@ int dialog_message(DIALOG *dialog, int m
if (msg == MSG_DRAW)
acquire_screen();
- force = ((msg == MSG_START) || (msg == MSG_END));
+ force = ((msg == MSG_START) || (msg == MSG_END) || (msg >= MSG_USER));
res = D_O_K;
--- /home/eric/cvs/allegro/docs/src/api._tx Thu Sep 18 11:47:00 2003
+++ allegro/docs/src/api._tx Thu Oct 16 10:56:53 2003
@@ -103,6 +103,8 @@ Changes between 4.0.x and 4.2.x series
it takes into account the bounding box to calculate the position which the
string is centered around. It previously used only the x field. And, as a
consequence, gui_ctext_proc is now expected to behave the same.
+<li>
+ dialog_message() now passes user messages to hidden objects.
</ul>
@heading