i had to put the global behind global. i was a mistake i looked over. so
no bug.
Op 23-1-2019 om 04:51 schreef Tom Glod via use-livecode:
has this been resolved?
when you moved the global declaration to the top it worked?
I keep an eye on reports like this because they are the most
worrisome
i had to put the global behind global, not behind local. it was a
mistake i looked over. so no bug.
Op 23-1-2019 om 04:51 schreef Tom Glod via use-livecode:
has this been resolved?
when you moved the global declaration to the top it worked?
I keep an eye on reports like this because they are
has this been resolved?
when you moved the global declaration to the top it worked?
I keep an eye on reports like this because they are the most
worrisome kinds of things.
But I always trust that the programmer will find the error in their ways.
On Mon, Jan 21, 2019 at 5:44 PM J. Landman Gay
no it should'nt you're right Jacque
only i forced myself months ago to put globals at the top and this stack
script was already older and i had putted locals at the top, so i
misplaced and overlooked 1 global
this was my fault, a global after some locals:
local tThis, tThat, tAnother, tAgain
On 1/21/19 12:06 PM, JJS via use-livecode wrote:
Foolishly i putted this global behind the locals on the top line. And
blindly trusting myself that it was correct i did not notice it.
I didn't realize the order mattered. Seems like it shouldn't.
--
Jacqueline Landman Gay | jac...@h
Thanks Kay for your detailed way of solving such issues, i'll keep that
in mind may i get a similar issue.
By the way i lately use Brian's script exporter, instead of doing it
manually. It works fast and great.
I always (well i force myself to) declare my globals at the top of a
script stac
You said you checked every card/button, but did you also verify the stack
script too?
Are you defining the global at the script level or inside a particular handler?
Thanks,
Brian
On Jan 19, 2019, 3:31 PM -0600, JJS via use-livecode
, wrote:
> Hi,
>
>
> i've never had this before and i believe i
On Sun, Jan 20, 2019 at 8:30 AM JJS via use-livecode
wrote:
> Because with another stack the same principe is working correct. Using
> LC902.
In the odd cases where I've seen this happen (not your problem, but
where the same code works in one stack but not another) my fallback
strategy is to:
c
Hi,
i've never had this before and i believe it is a stack fault rather than
an actual bug.
Because with another stack the same principe is working correct. Using
LC902.
With the current stack the global gLocalDbID of the next line is empty
once the new card is opened.
put revOpenDatab
