RE: lingo-l Language and DoubeByte Language

2004-05-13 Thread Kerry Thompson
Entry and display. CCJK Text entry means the user _must_ have the appropriate language system, either native or add-in like Twin Bridge. Literate Chinese means knowing about 4,000 characters--you need about 3,000 just to read newspaper, and a scholar will know 8,000-10,000. Japanese requires

Re: lingo-l javascript syntax

2004-05-13 Thread Colin Holgate
We all know there are faults to be found but I, for one, am very, very happy about JavaScript integration. I remember sitting in the sneak at the last UCON (1999? 2000? -- I think it was circa D6 because I was doing a lecture/workshop introducing behaviors) when an enthusiastic Director engineer

lingo-l [x-post] How do I get the metadata of a PowerPointPresentation?

2004-05-13 Thread Alexandre Cop
Hi all, Apologies to those who have received this email from another list... I need to find a way to read the following data in a PowerPoint presentation: Title, author, subject, comments. (that's the sort of thing you find when right-clicking the file in Windows and going into properties,

Re: lingo-l Language and DoubeByte Language

2004-05-13 Thread roymeo
At 05:14 PM 5/11/2004, you wrote: Does the project require data entry or just data display? Entry and display. Does the project need to save data, and if so, will the files be distributed between different users or stay on a particular machine (ie: are the files data files that may be exchanged

Re: lingo-l [x-post] How do I get the metadata of a PowerPointPresentation?

2004-05-13 Thread 2702NET
Hi Alex, This is just off the cuff - but have you looked into using BinaryIO Xtra from updateStage i.e. reading this information from the PowerPoint file directly? You would need the PowerPoint file specification which I assume is publicly available. Gilles On Thursday, May 13, 2004, at

Re: lingo-l Language and DoubeByte Language

2004-05-13 Thread Daniel Nelson
Hello Roy, Simply setting the font of a field or text member to a double byte font appears to allow text entry. I haven't produced a final product that allowed entry, and only experimented on Macintosh, but the experiments indicate that it is very easy (they explored using BIG5 and GB for

RE: lingo-l Language and DoubeByte Language

2004-05-13 Thread roymeo
The product has some character entry...file names, order stuff, etc. And there's also some character parsing like Using % to wash your clothes is . where they intend to have strings translated into multiple languages and hopefully still do some parse-replacing of characters. roy At 12:50 PM

lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread Mendelsohn, Michael
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.

RE: lingo-l Language and DoubeByte Language

2004-05-13 Thread Kerry Thompson
The product has some character entry...file names, order stuff, etc. And there's also some character parsing like Using % to wash your clothes is . where they intend to have strings translated into multiple languages and hopefully still do some parse-replacing of characters. The

Re: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread Jeff Gomes
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 (

Re: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread roymeo
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

RE: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread Thomas Higgins
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

RE: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread Mendelsohn, Michael
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

RE: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread Mendelsohn, Michael
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.

RE: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread Jeff Gomes
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

Re: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread Troy Rollins
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

RE: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread roymeo
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

Re: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread Troy Rollins
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

Re: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread roymeo
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,

Re: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread Troy Rollins
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

RE: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread Mendelsohn, Michael
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.

RE: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread Rob Adams
Don't think there's any way to do that. Re-installing Director would probably reset the symbol table to its original state. As mentioned previously, you shouldn't ever rely on the case of a symbol name. Rob From: Mendelsohn, Michael [EMAIL PROTECTED] Date: 2004/05/13 Thu PM 04:55:22

Re: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread John Mathis
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

RE: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread roymeo
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

RE: lingo-l fileIO changes T to t ?!?!?

2004-05-13 Thread Daniel Plaenitz
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