X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Sat, 27 Feb 2016 18:22:45 -0500 Message-Id: <201602272322.u1RNMjrQ001204@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: (geda-user AT delorie DOT com) Subject: Re: [geda-user] Re: re-instituting GetXY() References: <201602260114 DOT u1Q1EFRk019336 AT envy DOT delorie DOT com> <201602262010 DOT u1QKA2Hf024379 AT envy DOT delorie DOT com> Reply-To: geda-user AT delorie DOT com > Seems to work. So I guess doing things this way the &x and &y args aren't > used for anything, and the rest of the actions in the sequence know to get > the coordinates from a global somewhere? Yup. > It looks like there are only a handful of actions that set need_coord_msg > non-NULL. Is there any reason to have both mechanisms? I haven't run into > anything that seems to need multiple clicks. Sometimes an action itself needs a point, and provides a reason. It would fail without one, so it says so. Sometimes you mix many actions together, some of which need points, but the reason for the *mix* differs, so you can change the message the user sees. For example, the list of actions that converts a selection to an element needs a point for the element's mark, but none of the individual actions involved know that (IIRC the cut() needs a point, but it doesn't know it's being used to convert an element). In these cases, GetXY() lets you "document" a set of actions in a way that's meaningful to the user.