Re: [ROOTTALK] Event_t::fType values

From: Tom Roberts <tjrob_at_fnal.gov>
Date: Thu, 12 Jul 2007 09:40:35 -0500


Thanks, all. I just double-clicked on the name in the comment, and did searches and grep-s. I should have clicked on the type-name.

Tom Roberts

Ilka Antcheva wrote:

> Hi Tom,
> 
> All event types are included also in GuiTypes.h file but the name used 
> in Event_t was misleading. This will be fixed in cvs.
> 
> Cheers, Ilka
> 
> Tom Roberts wrote:

>> I am trying to use right- and middle- mouse clicks on a TGTextEntry. I
>> can Connect to its ProcessedEvent(Event_t*) signal, and can printf the
>> Event_t field values, but I have no idea what those numbers mean.
>> GuiTypes.h says "see EGEventTypes", but I cannot find that anywhere.
>> Pressing the button generates 5 events, and releasing it generates 1
>> more. From GuiTypes.h I can identify the button in fCode, and its bit
>> in fState, but the fType values are opaque. I want to be portable, so
>> just deducing the value from the printf does not seem like a good
>> idea. Where are these documented?
>>
>> Mouse enters TGTextEntry:
>> fType=5 fCode=0 fState=0x00000010
>>
>> Right button down:
>> fType=6 fCode=1 fState=0x00000410
>> fType=5 fCode=2 fState=0x00000410
>> fType=2 fCode=3 fState=0x00000010
>> fType=8 fCode=0 fState=0x00000005
>> fType=7 fCode=0 fState=0x00000000
>>
>> Right button released:
>> fType=3 fCode=3 fState=0x00000410
>>
>> Mouse leaves TGTextEntry:
>> fType=6 fCode=0 fState=0x00000010
>>
>>
>> Tom Roberts
>>

> Received on Thu Jul 12 2007 - 16:43:30 CEST

This archive was generated by hypermail 2.2.0 : Fri Jul 13 2007 - 17:50:01 CEST