#thanksEveryOneForAnsweringMySymbolQuestion
#THANKSEVERYONEFORANSWERINGMYSYMBOLQUESTION
- Michael M.
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL
PROTECTED] (Problems, email [EMAIL
All,
I wanted to put a final note on this thread for I have been to the mountain
and I have spoken with the wise one himself. I asked JHT (John Henry
Thompson, father of Lingo, coder extraordinare) a few questions about this
topic:
1. Where is that lookup table stored?
The symbol table is
Hi list...
Here's a weird one. The lingo below generates a preferences file if it
doesn't previously exist. The default prefs file (a prop list) is
theHeaderString. All well and good until it is read back in by FileIO
where property pT morphs from pT in the first list to pt in the second
list.
That's in the category of just the way Director works. The symbol table stores the
case of the first occurrence of any new symbol. Any future use/lookup is
case-insensitive, but the original case will always be returned. So you evidently had
a preexisting #pt. Now you get...
put symbol (
And symbols which exist in Director already are always going to be the way
they instantiate them. #member, never #Member
put #Member
-- #member
put #SpriTE
-- #sprite
At 02:40 PM 5/13/2004, you wrote:
That's in the category of just the way Director works. The symbol table
stores the case of
That's in the category of just the way Director works. The
symbol table stores the case of the first occurrence of any
new symbol.
Yup. This is easy to test using any new arbitrary symbol. Here's what I just
did in my Message window:
x = #USEALLUPPERCASEFORTHISTEST
put
Well, thanks for the feedback everyone! Regarding the case following
the case of the first occurrence, I went through all of my code and
nowhere do I have pt (my Lingo only has pT). So why might this still
happen when my first occurrence of this symbol is in fact pT?
Thanks,
Michael M.
[To
Just as an addendum to what I previously posted:
Clearglobals
Showglobals
-- Global Variables --
version = 10.0
put symbol(PT)
-- #pt
put symbol(PK)
-- #PK
put symbol(Po)
-- #Po
put symbol(mm)
-- #mm
put symbol(MM)
-- #mm
It seems the combination of letters pt/PT/pT/Pt always renders #pt.
1) It could be something Director already has in place.
2) It could be something you typed by mistake once, and now it has persisted from
session to session because of your continued use of #pT. Many things are stored as
symbols besides the things we directly declare as symbols, including
On May 13, 2004, at 3:45 PM, Mendelsohn, Michael wrote:
put symbol(PT)
-- #pt
put symbol(PK)
-- #PK
put symbol(Po)
-- #Po
put symbol(mm)
-- #mm
put symbol(MM)
-- #mm
It seems the combination of letters pt/PT/pT/Pt always renders #pt.
Hmm...it's as if Director has #pt reserved for something
The important idea here is that since you cannot guarantee the case of a
symbol, do not rely on the symbols to have the case you want them to be.
I BELIEVE these may be persistent with the movie, or something...so once
you use #booGERhead in a certain dir file, it stays in there somewhere and
On May 13, 2004, at 3:59 PM, Troy Rollins wrote:
I think you do somewhere in your code.
PUT symbol(PT)
-- #PT
And don't forget, once you've done this, even once, it is registered in
the symbol table that way. You would need to close Director and restart
to be sure. For instance, now that I
Actually, the symbol table follows the .dir (and cst's?) around. They are
more persistent than global variables.
Closing Director will not make it go away, unless you're only talking
playing in Director and not actual director files.
roymeo
At 04:27 PM 5/13/2004, you wrote:
On May 13, 2004,
On May 13, 2004, at 4:27 PM, Troy Rollins wrote:
You would need to close Director and restart to be sure.
Or, as Roy tested... even that doesn't work. You'd also have to open a
different or new project file.
--
Troy
RPSystems, Ltd.
http://www.rpsystems.net
[To remove yourself from this list, or
If that's the case, how can I edit the symbol table?
Actually, the symbol table follows the .dir (and cst's?) around. They
are
more persistent than global variables.
Closing Director will not make it go away, unless you're only talking
playing in Director and not actual director files.
EDT
To: [EMAIL PROTECTED]
Subject: RE: lingo-l fileIO changes T to t ?!?!?
If that's the case, how can I edit the symbol table?
Actually, the symbol table follows the .dir (and cst's?) around. They
are
more persistent than global variables.
Closing Director will not make it go away
And don't forget, once you've done this, even once, it is registered in
the symbol table that way. You would need to close Director and restart
to be sure. For instance, now that I have done the above in the message
window...
I think it is stored in the compiled script. So Recompile All
The important idea here is that since you cannot guarantee the case of a
symbol, do not rely on the symbols to have the case you want them to be.
You cannot edit the symbol table.
That symbol #pt is stuck that way. You could make a new Director movie and
copy everything over there.
You can
At 16:18 13.05.2004 -0400, roymeo wrote:
The important idea here is that since you cannot guarantee the case of a
symbol, do not rely on the symbols to have the case you want them to be.
I BELIEVE these may be persistent with the movie, or something...so once
you use #booGERhead in a certain
19 matches
Mail list logo
