Yes I have had situations where what the built in functions were returning were
not expected, and it screwed somethign up, which is why I do not rely on them.
It seems a bit ambiguous to me that "this stack" might return different things
depending on where the handler resides. By moving a script from a stack handler
to a front or backscript, this can cause problems.
Therefore I never use those built in calls, having a drop dead accurate way to
get what I want anyway.
> On Aug 9, 2017, at 09:53 , Paul Dupuis via use-livecode
> <firstname.lastname@example.org> wrote:
> I have handlers like these also. I have multiple work-arounds. You can
> use suspend and resume to preserve the defaultStack and restore it. Lots
> of way to work-around. I am curious if others have seen this and whether
> anyone ever found a reproducible recipe.
> So you have seen this behavior? In what versions of LC? Did you ever
> find a consistent recipe to reproduce it?
use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription