Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 07 FEB 1999 08:00:16PM Matt Crozier wrote:

Cameron,

To carry on from a discussion we had several years ago… I'm wondering if the example code you gave me is still valid in OI 3.7 ??

We sometimes get a VNAV on $OIWIN_GOTFOCUS. I suspect we're not passing enough parameters to RUN_EVENT. What confuses me is that PEEK_EVENT and RUN_EVENT seem to take different numbers of parameters.

Can you please tell me how many arguments I need to pass. Thanks,

Matt.

Subj: GET_EVENT Section: OInsight Design

To:  Vernon Systems Ltd, 100033,673	Saturday, 28 September 1996 09:59:07

From: Cameron Purdy RTI, 75300,2032 #131994

Matt,

It is very interesting … there are very few "atomic" elements in OI, and what you think of as

"low level" is often written in OI itself using other routines written in OI itself .. see the

example below.

Cameron. Revelation


subroutine Yield(void)

declare function Peek_Event

declare subroutine Run_Event

loop

while Peek_Event(AppID, ObjectID, ObjectClass, Event, p1, p2, p3, p4, p5, p6, p7, p8, p9)

Run_Event(Appid, ObjectID, ObjectClass, Event, p1, p2, p3, p4, p5, p6, p7, p8, p9)

repeat

return


At 07 FEB 1999 10:33PM Matt Crozier wrote:

Red Herring! - Turned out to be an unassigned return value on a routine called from the DEFAULT hook of a control. Thanks anyway,

Matt.

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/ac1905c0a3402e69852567120005849f.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1