Yes true - I had second thoughts after posting. I think I also agree with Monte though :)
Within the preOpenStack handler we haven't yet arrived - so the recent card should be as it is the recent card before actual going anywhere. But then the currentcard should not be already updated to return the value of the card you have not actually arrived at - the current card should return the value of the card you left. unfortunately the target returns the same as the current card - so we still have this informational hole in the middle where we cannot tell the value of the card we left before arriving so to speak - we get the one before and the one we will arrive to - but not the one we left. On 2 July 2016 at 16:09, Mark Wieder <[email protected]> wrote: > On 07/02/2016 07:20 AM, David Bovill wrote: > >> It is inconsistent. >> > > Unsurprisingly, I find myself agreeing with Mark Waddingham here (we Mark > Ws have to stick together). In preOpenCard you're still in transit, so you > haven't yet arrived at the destination card. In that case the card you came > from is still the current card. After the preOpenCard handler has finished, > the card you came from is added to the recent cards list and the > destination card becomes current. > > Does querying "the target" in the preOpenCard handler give you what you > want in addition to "the current card"? > > -- > Mark Wieder > [email protected] > > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
