Empty Field on Stack closure

[redfield]

Hi guys,
I was looking for a way to put an initial value into a Field on startup of the Stack. So what I did on Card 1 is this:

Code: Select all

on openCard
   set the text of fld f1 to 10
end openCard

And this seems to work fine. But I also want to empty another Field on the Card, when closing the Stack. So I tried this:

Code: Select all

on closeCard
   set the text of fld f2 to empty
end closeCard

This doesn't work though, the Field remains filled. I'm stuck again .

[Klaus]

Hi redfield,

if you do not SAVE the stack after emptying the field, it will open again in the state of the last SAVE.
Same with standalones, which cannot save themselves at all.

So just empty the field "on preopencard" or even "on preopenstack" and noone will be able to tell the difference!


Best

Klaus

[redfield]

Thanks Klaus, but seems I didn't get it yet.

I have now:

Code: Select all

on preOpenCard
   set the text of fld f1 to 10
   set the text of fld f2 to empty
end preOpenCard

When I open the stack and change f1 let's say to 20 and fill f2 with "xyz", then save, close and reopen, f1 shows value 10 (which is what I want) but f2 is not empty, it shows "xyz".

[Klaus]

Does this also happen if you quit LC after saving and then start LC and open that stack again?

[dunbarx]

Are you sure you have no other handlers in play? It sure seems that what you have should work just fine. I will be shocked if this is a real anomaly. The handler is just too simple and direct.

Craig

[redfield]

Your answers indicate that this should not be . So I double double checked everything and discovered having a typo in the name of the second Field. It's working fine now, thanks and sorry for the fuss!

[Klaus]

Okie Dokie!

But do yourself a favour and get used to put QUOTES around all strings like object names etc.:

Code: Select all

...
set the text of fld "f2" to empty
...

[dunbarx]

discovered having a typo in the name of the second Field.

LC did not throw an error when you tried to modify a non-existent field? There is still something odd here, even if not related to the original issue.

Craig

[redfield]

I was not precise, it was not a "typo", it was the name of a different field that I accidentally used (copy&paste). All is well with LC.