[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
> However object_message() is the regular way to send messages to dialog
> objects (all the gui code in the library code uses it).
When objects inherit from another, they usually call the procedure directly.
At least in the examples they do, perhaps the library does use the messages
properly.
>
Moreover using a
> special d_listchange_proc() object just for monitoring the change is a
> little bit weird.
I do similarly weird stuff to run multi-window dialogs, it's like
punctuation.
> > I can't reproduce the crash here, though (DJGPP under Win98), so it may
> > be a null pointer dereference if it crashes under CWSDPMI. Can you track
> > it down by placing liberal printf() statements everywhere?
Worse, it could be that address problem I was worrying about, (guibrella:
&d_proc != d.proc)
I will make a little test with CWSDPMI and post back.
> I don't have any crash either (DJGPP and MinGW). The problem I pointed out
> was fixed by Henrik's patch.
DJGPP with Win98? Never mind I can test my theory for sure.
Matt