You are probably right. But the workaround is so simple, putting an opaque green graphic in the group behind all the other objects, that it would be a lot of work to implement just so we didn't have to put a graphic in a group.
Bob S > On Jun 25, 2019, at 08:24 , dunbarxx via use-livecode > <use-livecode@lists.runrev.com> wrote: > > I suppose as long as one knows how it works, it can be dealt with. > > But there is an issue here, in that a group is not really a control, despite > what the dictionary says. A group has a rect, and one can tell if the > mouseLoc, say, is within that rect (and not necessarily within the rect of a > child control), but one cannot rely on any "ordinary" LC thinking to hold at > all. > > I understand that a group is merely a group of controls. If it was a > ghostLike object that only did that, then well and good. > > But since it interacts with those controls intrinsically (as, for example, > the way radio buttons behave "natively") and owns most "ordinary" control > properties, well then, dammit, if one makes it opaque and green, it ought to > respond to mouse events. > > Craig _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
