Dar Scott wrote 02.12.20 10:09 AM$B!'(B
(B>The problem is really the third case. If the groups are not
(B>backgrounds, they are treated as such in the message path as far as
(B>whether the backgrounds are after the card.
(B>
(B>Consider this card: card{ grpA( btn1 ), btn2, bgB( btn3 ) }
(B>
(B>Background bgB is in the path of btn3 and btn2, but not btn1.
(B>
(B>Suppose I have a background that does some navigation, but also blocks a
(B>particular key stroke from going to the default interpretation. If I
(B>put some fields on the card, the key is blocked for those fields. (I'm
(B>just guessing this will work.) But suppose I make a numerical field
(B>with up-down buttons, all grouped and I put that on the card. Maybe I
(B>got it from a card of many such custom controls and I forgot it was a
(B>group. The key stroke is not blocked.
(B
(B
(BI may be to have found a solution.
(BIt is written by a help as follows...
(B
(B-->
(BIf you want a handler in a group$B%f(Bs script to affect only the objects in
(Bthe group, place the following statement at the beginning of the handler:
(B
(B if the owner of the target is not me then pass message
(B
(BThis filters out any objects that are not part of the group.
(B<--
(B
(BHelp > Revolution Documentation > (Road Map) > Development Guide >
(BObjects & Messages > ( About... ) > groups and backgrounds
(B
(B
(B
(BUDI
([EMAIL PROTECTED]
(Bhttp://member.nifty.ne.jp/UDI/
(B_______________________________________________
(Buse-revolution mailing list
([EMAIL PROTECTED]
(Bhttp://lists.runrev.com/mailman/listinfo/use-revolution
