Most of what I am looking at is just keystroke events.  probably can  
all be done in the On Dialog functions

Thanks for the information.
All good to hear.

~ steve

On Aug 23, 2007, at 5:33 PM, Brian Stevens wrote:

>
> On Aug 23, 2007, at 1:46 PM, Steve wrote:
>
>> Brian,
>>
>> On Aug 23, 2007, at 12:24 PM, Brian Stevens wrote:
>>
>>> 1. On Mouse  and On Event - not implemented yet, however a lot  
>>> this work can be done in ON Dialog.
>>
>> Are these going to be implemented in FBtoC?
> On Mouse is just a matter of time. On Event is a little stickier.  
> Before I explain, would you list for for us which events you  
> intercept in your ON EVENT function?  That would really help, and  
> its likely we can provide alternatives if you are not wed to ON EVENT.
>
>
> Some background:   ON EVENT essentially provides the FB programmer  
> with a chance to look at events (via an event record) BEFORE they  
> are processed by the standard FB event runtime (i.e. ON DIALOG  
> etc.) .  Since the FB programmer is expecting what today is  
> considered an old style event record, FBtoC has to request a  
> translation of the EventRef (probably via TB  call  
> ConvertEventRefToEventRecord ) to an event record.  
> ConvertEventRefToEventRecord  combined with IsEventInMask  
> (Determines whether an event reference matches a WaitNextEvent- 
> style event mask) will probably give us what we need (although  
> Apple docs imply not all events are translated). Technically, it is  
> possible for FBtoC to pass to the user's event handler (i.e. the  
> target of your ON EVENT  FN DoMyEventStuff) an event record.
>
> So, to answer your question more directly, it is probably more a  
> question of *when* ON EVENT will be implemented and not if.  
> However, there might be limitations depending on how it is  
> implemented. When depends on whether someone on the team decides to  
> tackle it.
>
>
> Brian S.
>
> --
> To unsubscribe, send ANY message to: futurebasic- 
> unsubscribe@...
>