As far as the pie charts go.. A workaround is to create the required ovals one at a time and import an image from each, then stack THOSE up.
Or alternatively use the ovals, stack them, group them, and have a list of background colors used in each, and then in the group mouseup handler use the mousecolor to determine what/where was clicked. To be able to hit an area that has no oval color would require one more hoop to be jumped through. Place a full oval matching background color behind the pie segments that can catch a click in the "empty" location (still using the mousecolor) Which makes me think, how about a new object. An oval with definable color arcs. 0 to 85 blue, 85 to 270 red, 270 onward green. (or an innocuous grey meaning no data defined for that chunk) Then one could still check the mousecolor to determine a clicks result. The negative of this method is that one couldn't explode the pie chart. On Wed, Sep 27, 2017 at 10:48 AM, Sannyasin Brahmanathaswami via use-livecode <use-livecode@lists.runrev.com> wrote: > marvelous, very important thread…in mobile, it's all about the touch msg… > > yes "all of the above" the enhancement request to allow margins for > widgets stands as still useful but plays directly into the other scenarios > described here. And though separate "desires," they do over lap > > e.g. As it is now, the entire rect of an SVG widget is it's hit box. > Hence the request for margins… which is "it's own solution" > > But then, this: > > "When they're stacked on top of each other the transparent part of the > rect is still the object under the cursor, and so obscures what's > underneath." > > Having SVG on top of a graphic or vice-versa is, will be, a common use > case, which is yet another scenario. > > you may *not* want the mouse event to pass through the "transparent" > area. to objects below, objects below being "eye-candy" (gradient > backgrounds etc.) > > How Mark will provide a solution for "all of the above" will be > interesting to see. > > > Richard wrote: > > And where an SVG widget needs a clickable region larger than its > bounds, > the SVG widget would need to be enhanced to provide that. > > All of these are practical desires, but each has its own solution. > > _______________________________________________ > 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 _______________________________________________ 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