Colin Holgate wrote: > The way that this problem is handled in sort other tools is to have a > definable hit area for each control (usually those would be buttons). > You can set the idle, over, and pressed versions of the button’s > image, and also you can set the hit area image. > > LiveCode already has a way to do most of that, couldn’t the hit area > be another entry I the inspector’s icons section?
This seems like a viable option, easy to use for a wide range of use-cases and presumably within reasonable cost for the engine team to implement, since it would be a variant of the existing code used to calculate hit regions from the alpha channel.
-- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ____________________________________________________________________ ambassa...@fourthworld.com http://www.FourthWorld.com _______________________________________________ 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
