Agreed - its' the inconsistency that is problematic. Also the inability to establish where you have come from before rendering the contents of the display is a fundamental hole in the language - as we simply have no access to the recent card here. Whether we get this by referring to the current card in a preOpenStack handler (makes sense to me), or by using the recent card is not so important - but we DO need to be able to know where we have come from.
On 2 July 2016 at 09:47, Monte Goulding <mo...@appisle.net> wrote: > Looking at your report I'm not really sure if the bug is in the recent > card or the current card. If preOpenCard is before the card is open then > there's a good argument that it's the latter... > > Of course either may be an anomaly that may be difficult to do anything > about. > > Cheers > > Monte > > Sent from my iPhone > > > On 2 Jul 2016, at 6:34 PM, David Bovill <david@viral.academy> wrote: > > > > In a preOpenCard handler I cannot find the name of the recent card - the > > card that you "came from". As far as i can tell this is a very basic bug > > that goes back to at least version 7. > > > > Does anyone have a work around The only thing i can think of is to do my > > own logging in an openCard or closeCard handler. is there a sane reason > why > > preOpenCard is not reporting the value correctly or another way to get > the > > value of the recent card? > > > > > > I filed this as a bug - > http://quality.livecode.com/show_bug.cgi?id=17939 > > > >> On 1 July 2016 at 19:39, David Bovill <david@viral.academy> wrote: > >> > >> on preOpenCard > >>> put the short name of recent card > >>> pass preOpenCard > >>> end preOpenCard > >> > >> > >> Why is the recent card when specified in a preOpenCard handler the name > of > >> the current card, while it is the recent card if the same script is > called: > >> > >> on openCard > >>> put the short name of recent card > >>> pass openCard > >>> end openCard > >> > >> Given that preOpenCard is called before actually displaying the card and > >> the openCard handler being called this seems wrong. Is this behavior > >> present in older versions of LC - or is this a bug? > > _______________________________________________ > > 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 > _______________________________________________ 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