I mentioned wd 'wait' because it can do part of what I am trying to
accomplish. I want to take complete control over the message loop. For
example I want something like the following in win32:
while(1) {
GetMessage(...)
DispatchMessage(...)
}
wd 'wait' is somewhat like GetMessage with the undesired side effect of
making the current form modal and ignoring all the other forms. So,
essentially what I want to do is wait for an event.
The reason I want to do this and not use the standard J event handling
mechanism or override wdhandler is because this way I can make my entire gui
functional and functional level from the J perspective (i.e. tacit).
On Mon, Dec 15, 2008 at 6:04 PM, Eric Iverson <[email protected]>wrote:
> You'll probably need to describe your problem in more detail. My first
> response is that you shouldn't be using wd'wait'. It is rarely required and
> often its use indicates that a slightly better view of the overall problem
> would remove the requirement.
>
> On Mon, Dec 15, 2008 at 10:31 AM, Thomas Costigliola <[email protected]
> >wrote:
>
> > Is there a facility or some work around to wd 'wait' that allows you to
> > wait
> > for a message from all forms without making any of them modal?
> > ----------------------------------------------------------------------
> > For information about J forums see http://www.jsoftware.com/forums.htm
> >
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
>
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
