Re: [Fxruby-users] Message Identifiers, Types, etc again.
Status: Inactive
Brought to you by:
lyle
From: Sander J. <sa...@kn...> - 2003-06-13 13:02:13
|
On Friday 13 June 2003 07:44 am, Hugh Sasse Staff Elec Eng wrote: > Just when I thought I was no longer confused about this: > > On Thu, 12 Jun 2003, Hugh Sasse Staff Elec Eng wrote: > > OK, reading this in conjunction with paragraphs 3 and 4 of > > > > http://www.fox-toolkit.org/messages.html > > > > it seems that message_id is actually the sender of the message, and > > message type is actually the message itself (not counting associated > > data). I would have called the message itself the message_id, > > Well, it is not as simple as that. The FXRuby API docs for > FXShutter, FXShutterItem, FXScrollbar and FXList at least refer to > Message Identifiers which are constants, and are not names of the > originating objects. So should these be called Message Types for > consitency with other FOX docs, or what? > > Hugh a message consists of a type and a id. Sometimes called the selector. In C++ we have the following macros to get the type and id from a selector: FXSELTYPE(selector) FXSELID(selector) In constructors of widgets, you normally have to input a target and selector. In that case, the selector is only the ID. Its still named this way because of historically reasons. Also "getSelector" would give you back the ID. Sander > > ------------------------------------------------------- > This SF.NET email is sponsored by: eBay > Great deals on office technology -- on eBay now! Click here: > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Fxruby-users mailing list > Fxr...@li... > https://lists.sourceforge.net/lists/listinfo/fxruby-users -- "Mother, should I run for President? Mother, should I trust the government? Mother, will they put me in the firing line? Ooooowaa Is it just a waste of time?" -- Pink Floyd "The Wall" |