lingo-l All those DLLs
Hi list... How's everyone today? Regarding Dirapi.dll, Iml32.dl, msvcrt.dll and Tbrsrc.dll, is it better to have them sitting next to the projector or within the xtras folder? And regarding my DLLs for my onStage xtra, Proj.dll and OnStage.dll, I believe those go next to the projector, right? thanks, 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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l All those DLLs
with the onstage dlls, yes they go next to the projector. I recall including Tbrsrc.dll as well julian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mendelsohn, Michael Sent: 15 July 2004 13:44 To: [EMAIL PROTECTED] Subject: lingo-l All those DLLs Hi list... How's everyone today? Regarding Dirapi.dll, Iml32.dl, msvcrt.dll and Tbrsrc.dll, is it better to have them sitting next to the projector or within the xtras folder? And regarding my DLLs for my onStage xtra, Proj.dll and OnStage.dll, I believe those go next to the projector, right? thanks, 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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!] [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l All those DLLs
How's everyone today? Good. You? Regarding Dirapi.dll, Iml32.dl, msvcrt.dll and Tbrsrc.dll, is it better to have them sitting next to the projector or within the xtras folder? I think it's cross platform consistent to put them beside the projector. Either macos or windows will also look in the xtras folder (windows ?). -- Cole [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l All those DLLs
May I suggest you try with everything in the xtras folder...don't know about onstage or Tbrsrc, but I keep all the others in xtras. John Mathis Regarding Dirapi.dll, Iml32.dl, msvcrt.dll and Tbrsrc.dll, is it better to have them sitting next to the projector or within the xtras folder? And regarding my DLLs for my onStage xtra, Proj.dll and OnStage.dll, I believe those go next to the projector, right? [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l All those DLLs
yep, me too.. all in the Xtra folder, 'till now no problems whatsoever. J. -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] John Mathis Verzonden: donderdag 15 juli 2004 16:17 Aan: [EMAIL PROTECTED] Onderwerp: Re: lingo-l All those DLLs May I suggest you try with everything in the xtras folder...don't know about onstage or Tbrsrc, but I keep all the others in xtras. John Mathis Regarding Dirapi.dll, Iml32.dl, msvcrt.dll and Tbrsrc.dll, is it better to have them sitting next to the projector or within the xtras folder? And regarding my DLLs for my onStage xtra, Proj.dll and OnStage.dll, I believe those go next to the projector, right? [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!] [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l All those DLLs
Onstage.dll and tbrscr.dll are OnStage xtras and go next to the projector. The other four I just put in the xtras folder, and no playback difference. Thanks, all. How's everyone today? Good. You? Fine, thanks! - MM [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l All those DLLs
ummm what dll files? I've never included those dll's with any project before- is this a MX 2004 thing? Thank you, Stephen Ingrum [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] www.LeagueofDesign.com http://www.leagueofdesign.com http://www.leagueofdesign.com Johan Verhoeven wrote the following on 7/15/2004 9:39 AM: yep, me too.. all in the Xtra folder, 'till now no problems whatsoever. J. -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] John Mathis Verzonden: donderdag 15 juli 2004 16:17 Aan: [EMAIL PROTECTED] Onderwerp: Re: lingo-l All those DLLs May I suggest you try with everything in the xtras folder...don't know about onstage or Tbrsrc, but I keep all the others in xtras. John Mathis Regarding Dirapi.dll, Iml32.dl, msvcrt.dll and Tbrsrc.dll, is it better to have them sitting next to the projector or within the xtras folder? And regarding my DLLs for my onStage xtra, Proj.dll and OnStage.dll, I believe those go next to the projector, right? [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!] [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!] [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l All those DLLs
On Jul 15, 2004, at 11:12 AM, Stephen Ingrum wrote: ummm what dll files? I've never included those dll's with any project before- is this a MX 2004 thing? For fast start projectors, the DLLs are external. -- Troy RPSystems, Ltd. http://www.rpsystems.net [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
lingo-l Do MX 9 and MX 2004 co-exist?
The Upgrade Guide on the MM site doesn't mention this. Can someoone please tell me if the MX 9 continues to function normally on a Windows XP machine where the new MX 2004 is installed? Thanks! Slava [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l system disk
thanks guys, best nik ___ Reduce your company's IT costs today with Officemaster. Sign up for a free trial! http://www.officemaster.net [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l Do MX 9 and MX 2004 co-exist?
Yup, I have both installed on WinXP without an issue... Only irritating thing is that both icons look identical, so I had to change the one for the mx2004 exe just to make life easier :0) ~Mathew Slava Paperno wrote: The Upgrade Guide on the MM site doesn't mention this. Can someoone please tell me if the MX 9 continues to function normally on a Windows XP machine where the new MX 2004 is installed? Thanks! Slava [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l All those DLLs
The DLL files mentioned are for creating a Fast Start Projector (see http://www.macromedia.com/support/director/ts/documents/d8_fast- start_stub_proj.htm or search TechNote #14431) in which the DLL's are included as external files instead of being packaged into the projector. As I recall, this goes back to D5 or D6, but wasn't documented by MACR until D7. Jeremy Aker On Jul 15, 2004, at 11:12 AM, Stephen Ingrum wrote: ummm what dll files? I've never included those dll's with any project before- is this a MX 2004 thing? Thank you, Stephen Ingrum [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] www.LeagueofDesign.com http://www.leagueofdesign.com [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l All those DLLs
For fast start projectors, the DLLs are external. There's more to it than that. It's a matter of insuring that your projector plays at all. The scenario: a projector is an executable, and it loads the .dll (dynamic link library) files at runtime. Anybody who has programmed in C/C++ knows all about that. When Windows looks for a .dll, it looks in certain folders, in this order: - The directory where the executable module for the current process is located. - The current directory. - The Windows system directory. - The Windows directory. - The directories listed in the PATH environment variable. Now, here's the rub. Sometimes installers will put Dirapi.dll, Iml32.dl, and/or msvcrt.dll into the Windows system directory. If somebody has an old version that's incompatible with your projector, and you don't provide the right version (in your executable folder), your projector may fail, or you may get weird error messages. Msvcrt.dll is a Microsoft C/C++ runtime library. I believe Director needs the version from Visual C++ 6.0 or later. Whichever one is in your Director program directory is the right one (Director itself, not your projector). I believe dirapi.dll and iml32.dll are Macromedia dll's. I'm not sure about Tbrsrc.dll. I can see how it would affect fast start projectors. If the .dll is right there, your projector doesn't have to ask Windows to go looking for it. I don't see how it can help having it in the xtras directory, though, unless they are directly associated with one of the xtras. I have always put them in the projector folder. Cordially, Kerry Thompson [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l All those DLLs
On Jul 15, 2004, at 12:18 PM, Kerry Thompson wrote: For fast start projectors, the DLLs are external. There's more to it than that. It's a matter of insuring that your projector plays at all. But if the projector is not Fast Start, aren't the DLLs simply included within the executable? -- Troy RPSystems, Ltd. http://www.rpsystems.net [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
lingo-l multilanguage project
Perhaps this is the wrong forum but I know there are quite a few international folks on this list and others who have done quite a few international projects... Anyway, I am about to embark upon a multilanguage project with multilanguage installers and had a few questions about double-byte fonts. We tend to use flash alot for UI stuff, and seeing how it generally supports unicode, we think that would be the best route to take. There is also a web-based component (mini-site) to this too, so we can leave those flash assets as swfs on the server and be able to migrate easily across web to disc in our workflow. I know I can use standard ttf fonts and flash will embed the characters that are used in static text fields, but what about dynamic input text with double-byte characters? One localization that we are doing is Japanese, and I know there are 4 different scripts for the language, but generally what is the best script to use, Romanji? Our audience should be business people and from my menial research, most of this audience SHOULD be able to read Romanji lest the be considered illiterate. I certainly don't want to embed the whole 22 MB of Arial Unicode into a flash movie being played over the web, but it's not exactly easy to restrict the characters that ARE embedded in an input field (other than latin stuff) without listing all of them. Any pointers? Thanks, ~Mathew [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l All those DLLs
But if the projector is not Fast Start, aren't the DLLs simply included within the executable? No, I don't think so. It's been 4-5 years since I've programmed in C++, so I'm not certain, but I'm pretty sure things are still the same. First, look at the name--dynamic link library. That suggests that it's linked dynamically, i.e. at run time. The idea of a .dll is to have some code that different programs can use. The msvcrt (for Microsoft Visual C Run Time) dll is a good example. Virtually every C/C++ program written with Visual C++, including Director, uses that runtime library. Some Visual Basic programs use it too--maybe a lot of them. If you want to use a .dll in a C/C++ program, you generally specifically load it. I forget the syntax, but it's something like loadLibrary(library.dll). There is such a thing as a statically-linked dll, but I'm not familiar enough with their use to talk about them. They may be included in the executable, but I believe they are less often used. When you create an executable in C/C++, it's typically at two-step process. First, you compile all your source code files. That turns them into machine language, but with a lot of unresolved references--objects, variables, methods, etc. in other source files and .dll's. The second step is to link them all together. That resolves the references. Together, the compile-link process is usually called building. That typically does not include the .dll in the executable. In fact, if you don't specifically load the .dll in your code, at the right time, you will get errors, either at run time or during the build (I don't remember exactly--it's been too long). HTH. Cordially, Kerry Thompson [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l All those DLLs
On Jul 15, 2004, at 1:04 PM, Kerry Thompson wrote: That typically does not include the .dll in the executable. In fact, if you don't specifically load the .dll in your code, at the right time, you will get errors, either at run time or during the build (I don't remember exactly--it's been too long). So, then, you are suggesting that there is no such thing as a single icon self-contained executable Director movie on Windows? I don't think that is the case. If you don't mind a slow start up, all the xtras, the DLLs, the movie, the casts (if internal), can all be wrapped into one runtime file, as far as I know. That is the reason that a ghost xtras folder appears temporarily when you run one of them - no? Note that I do the fast start routine myself, and externalize everything, but I don't believe you HAVE to, as you've described. I think in the case where you don't, the projector behaves kind of like a self-extracting executable, which extracts, runs, then does a clean up routine. But then, I could be wrong. -- Troy RPSystems, Ltd. http://www.rpsystems.net [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l multilanguage project
Perhaps this is the wrong forum but I know there are quite a few international folks on this list and others who have done quite a few international projects... Anyway, I am about to embark upon a multilanguage project with multilanguage installers and had a few questions about double-byte fonts. May I suggest that you pick up a copy of the July issue of MX Developer's Journal? They have a section devoted to multilingual projects this month. There are articles by luminaries such as James Newton, Tab Julius, and even ordinary guys like (ahem) me. We tend to use flash alot for UI stuff, and seeing how it generally supports unicode, we think that would be the best route to take. Are you going to use the swf files in Director? You won't be able to pass strings back and forth, because Director doesn't support Unicode. There are rather intricate workarounds--search the archives for the past 6 months or so for Mark Jonkman. If you're going to do text input in Director, it's pretty much taken care of by the system, but you'll get multibyte Japanese text encoded in EUC or Shift-JIS. Once again, (ahem) my article contains more details. what about dynamic input text with double-byte characters? One localization that we are doing is Japanese, and I know there are 4 different scripts for the language, but generally what is the best script to use, Romanji? The only way to do a legitimate Japanese product is to support all 4 Japanese scripts: kanji, hiragana, katakana, and romaji. Romaji is the least important of the four, and absolutely cannot be used as the sole input. You would be laughed out of the Japanese market. You don't have to do much to support Japanese input, though. Japanese Osen (Windows, Mac) have built-in IME's (Input Method Editor). When a user types in some text, you'll get whatever he types in, and the system will recognize it as kanji, hiragana, etc. Cordially, Kerry Thompson [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l All those DLLs
All, Now, here's the rub. Sometimes installers will put Dirapi.dll, Iml32.dl, and/or msvcrt.dll into the Windows system directory. ... While this is correct, somebody has installers somewhere that do this, it doesn't _appear_ to be ours (MACR's) that do this. We recently faced some nasty bugs where the problem all boiled down to the end user having our DLL files in the Windows/System directory causing just this error. For Macromedia-provided DLL's you can: - Director 7 - they must go next to the projector - Director 8 and newer - they can go next to the projector or in a Xtras folder We made that change during D8 so folks could clean-up the app level folder a bit and have the dangling external files (Xtras and DLL's) collected into one folder (is that a sufficient reason Kerry? Maybe yes, maybe no, but folks asked for it so we made the change). Please note again that I'm only referring to our DLL files as discussed in the fast-start projector tech note that was mentioned. Hope that helps. Cheers, Tom Higgins Product Manager - Director Team Macromedia ... [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l All those DLLs
Troy's interpretation, I believe, is the same as mine. From what I know on OS9 and PC systems standalone projectors could be just that...standalone. Anything needed was contained within the exe. Now with OSX, I believe the preferred method of creating projectors is with fast start projectors in a bundle, which require the proper libraries to be present in the bundle. I don't believe OS9 used fast start projectors...but I may be wrong. PC projectors can still be standalone with no dll or xtra folders needed. All that is bundled into the exe (hence the size increase) and is unpackaged to a temp folder at runtime. Perhaps that is the static dll reference that kerry mentioned. ~Mathew Kerry Thompson wrote: But if the projector is not Fast Start, aren't the DLLs simply included within the executable? No, I don't think so. It's been 4-5 years since I've programmed in C++, so I'm not certain, but I'm pretty sure things are still the same. First, look at the name--dynamic link library. That suggests that it's linked dynamically, i.e. at run time. The idea of a .dll is to have some code that different programs can use. The msvcrt (for Microsoft Visual C Run Time) dll is a good example. Virtually every C/C++ program written with Visual C++, including Director, uses that runtime library. Some Visual Basic programs use it too--maybe a lot of them. If you want to use a .dll in a C/C++ program, you generally specifically load it. I forget the syntax, but it's something like loadLibrary(library.dll). There is such a thing as a statically-linked dll, but I'm not familiar enough with their use to talk about them. They may be included in the executable, but I believe they are less often used. When you create an executable in C/C++, it's typically at two-step process. First, you compile all your source code files. That turns them into machine language, but with a lot of unresolved references--objects, variables, methods, etc. in other source files and .dll's. The second step is to link them all together. That resolves the references. Together, the compile-link process is usually called building. That typically does not include the .dll in the executable. In fact, if you don't specifically load the .dll in your code, at the right time, you will get errors, either at run time or during the build (I don't remember exactly--it's been too long). HTH. Cordially, Kerry Thompson [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l All those DLLs
All, But if the projector is not Fast Start, aren't the DLLs simply included within the executable? Standard projectors contain copies of all the needed DLL's. Compressed projectors (not found in MX'04 anymore) contained compressed copies of the needed DLL's. Shockwave projectors don't contain any of the needed DLL's. Upon projector launch the code follows this detection process: 1. Look inside the projector, are the DLL's there? If yes, unpack them to a temp directory and link against those temporary copies. If not proceed to step 2. 2. Look next to the projector, are the DLL's there? If yes, load and use those copies. If not proceed to step 3. 3. (D8 and newer only, if in D7 go to step 4) Look for a folder named Xtras next to the projector, are the DLL's there? If yes load and use those copies. If not proceed to step 4. 4. Check the system directory for copies of the needed DLL files, if found load and use them, if not the projector launch fails. It is in step 4 that we run into the problem mentioned by Kerry. In the normal situation the only copies of our DLL's found in the System directory should be found in our own Shockwave player folder, but trouble occurs when the system first detects a copy in Windows/System (as opposed to finding the right copies in Windows/System/Macromed/Shockwave X/). So placing the DLL files either next to the projector or in a separate Xtras folder you bypass any potential for system confusion. Cheers, Tom Higgins Product Manager - Director Team Macromedia ... [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l get and set pixel.
I am not sure what you mean by ink modes in copypixels. Any examples? Here ya go: destImg.copyPixels(srcImage,destRect,srcRect,[#ink: 36]) The above applies ink 36 (bgtrans) to the copyPixels operation, there are many options you can use here (blend levels, masking options, and more). This one is actually in the documentation! To be safe, I checked the MX docs before saying that last bit... ;) Cheers, Tom Higgins Product Manager - Director Team Macromedia ... [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l All those DLLs
So, then, you are suggesting that there is no such thing as a single icon self-contained executable Director movie on Windows? I don't think that is the case. You may be right--I'm not sure. I don't think the .dll's are included in a normal projector, but I'm too far away from the C/C++ world to know for sure. The Macromedia tech notes I've read suggest you may be right. I know that for a fast-start projector, media and xtras are packaged externally, and Shockwave compression is used. Because of the Shockwave compression, you have to have the .dll's externally. I include the .dll's in my program directory because I've had problems in the past with conflicts with outdated versions. I'm not certain that is still the case, but it certainly does no harm. Cordially, Kerry Thompson [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l All those DLLs
Tom, Shouldn't your Point 4 include and any subfolders within it? I've always used subfolders within the Xtras folder but never knew how many levels down the projector looks. It might be useful to know. Thanks for an excellent writeup, I'll save it. Slava At 10:36 AM 7/15/04 -0700, you wrote: Upon projector launch the code follows this detection process: 1. Look inside the projector, are the DLL's there? If yes, unpack them to a temp directory and link against those temporary copies. If not proceed to step 2. 2. Look next to the projector, are the DLL's there? If yes, load and use those copies. If not proceed to step 3. 3. (D8 and newer only, if in D7 go to step 4) Look for a folder named Xtras next to the projector, are the DLL's there? If yes load and use those copies. If not proceed to step 4. 4. Check the system directory for copies of the needed DLL files, if found load and use them, if not the projector launch fails. ... [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l All those DLLs
1. Look inside the projector, are the DLL's there? If yes, unpack them to a temp directory and link against those temporary copies. Aha! Now it makes sense. The .dll's are packaged with the .exe, just like the xtras, but are not really part of the core executable. They're still loaded at runtime, after unpacking. It appears they aren't statically linked. Excellent write-up, Tom. Thanks. It clears up a lot. Cordially, Kerry Thompson [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l All those DLLs
Slava, Shouldn't your Point 4 include and any subfolders within it? For the DLL files I think the answer is no, they might have to be top-level in the Xtras folder (someone want to test that?). For any Xtras then the answer is yes, up to five levels of sub-folders IIRC. Cheers, Tom Higgins Product Manager - Director Team Macromedia ... [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l All those DLLs
Aha! Now it makes sense. The .dll's are packaged with the .exe, just like the xtras, but are not really part of the core executable. They're still loaded at runtime, after unpacking. It appears they aren't statically linked. Bingo, it's that unpack then linkload bit you weren't clear on. Glad to read it's sorted and that my info helped. Cheers, Tom Higgins Product Manager - Director Team Macromedia ... [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l Do MX 9 and MX 2004 co-exist?
Hi Slava I'm currently running Director 8, 8.5, MX and MX 2004 on my WinXP Pro machine with no problems at all. The only thing you'll find is the the file extensions will map themselves to the last version you installed so you'll get a couple of niggling problems when double-clicking files or using Recent Documents to open them. Easily rectified by editing the file types manually (I've set up Open With links to all 4 versions) or just open the project from within the Director app appropriate to that project. Ross [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l All those DLLs
Tom: Thanks for the great answer. Slava: I develop on Windows, and everything that goes in my xtras folder goes inside a subfolder called pc, so that means an extra level into the xtras folder for my dlls, and it worked fine. Regards all, - 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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l All those DLLs
Bingo, it's that unpack then linkload bit you weren't clear on. Glad to read it's sorted and that my info helped. Let me add this: If your standard projector starts, and then crashes (or perhaps is rudely quit) you will leave the dlls in the temp folder that was created, wasting space. Nothing routine cleaning of your temp folder wouldn't fix, but something to keep in mind. John [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l get and set pixel.
At 20:36 Uhr +0300 15.07.2004, thor wrote: I am not sure what you mean by ink modes in copypixels. Any examples? it depends on what you're after with the: At 13:47 Uhr +0100 14.07.2004, thor wrote: rgbval = member(firstImg).image.getPixel(xx, yy) -- some calculations here and then member(secondImg).image.setPixel(xx,yy, newrgbval) '-- some calculations here and then' the simplest example would be copying a black image with reverse ink to reverse the image. but you can also isolate colors with not reverse ink or achieve other results when using different inkmodes after another. you can also desturate by copyPixeling into a #grayscale image or posterize by copypixeling into an 8 bit image with a custom palette. there is so much possible in director since the introduction of IL, that it is for me the top feature, which was ever added to director. I can't imagine working a single day without an IL operation. -- ||| a¿ex -- [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l All those DLLs
Slava: I develop on Windows, and everything that goes in my xtras folder goes inside a subfolder called pc, so that means an extra level into the xtras folder for my dlls, and it worked fine. Thanks for that confirmation Michael. Cheers, Tom Higgins Product Manager - Director Team Macromedia ... [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l multilanguage project
Just took a look at the most recent version, but the latest digital version accessible via their site is June's issue (the one with tooltips in director by irv). I guess the digital versions lag behind the print versions... Fortunately the unicode will be self contained within flash, so that shouldn't be an issue, and most input is coming through flash input text fields - which was my main concern about having to embed big-ol double-byte fonts into swfs for either director or web use. The concern being that if I have to embed the double-byte font characters (like I usually do on my english projects to make sure it looks the same across machines), then the swf could get enormous. Thanks for the info about the hiragana and katakana info... Would it be safe to say that most translation agencies worth their salt should provide material in all 4 scripts? Thanks, ~Mathew Kerry Thompson wrote: Perhaps this is the wrong forum but I know there are quite a few international folks on this list and others who have done quite a few international projects... Anyway, I am about to embark upon a multilanguage project with multilanguage installers and had a few questions about double-byte fonts. May I suggest that you pick up a copy of the July issue of MX Developer's Journal? They have a section devoted to multilingual projects this month. There are articles by luminaries such as James Newton, Tab Julius, and even ordinary guys like (ahem) me. We tend to use flash alot for UI stuff, and seeing how it generally supports unicode, we think that would be the best route to take. Are you going to use the swf files in Director? You won't be able to pass strings back and forth, because Director doesn't support Unicode. There are rather intricate workarounds--search the archives for the past 6 months or so for Mark Jonkman. If you're going to do text input in Director, it's pretty much taken care of by the system, but you'll get multibyte Japanese text encoded in EUC or Shift-JIS. Once again, (ahem) my article contains more details. what about dynamic input text with double-byte characters? One localization that we are doing is Japanese, and I know there are 4 different scripts for the language, but generally what is the best script to use, Romanji? The only way to do a legitimate Japanese product is to support all 4 Japanese scripts: kanji, hiragana, katakana, and romaji. Romaji is the least important of the four, and absolutely cannot be used as the sole input. You would be laughed out of the Japanese market. You don't have to do much to support Japanese input, though. Japanese Osen (Windows, Mac) have built-in IME's (Input Method Editor). When a user types in some text, you'll get whatever he types in, and the system will recognize it as kanji, hiragana, etc. Cordially, Kerry Thompson [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!] [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l multilanguage project
Thanks for the info about the hiragana and katakana info... Would it be safe to say that most translation agencies worth their salt should provide material in all 4 scripts? Probably, but it's more accurate to say they would provide it as a Japanese speaker would expect to see it. Japanese isn't either-or. They mix the four script types. People's names, for example, are often written in Kanji for the family name, and Hiragana for the given name. Kanji are the ideograms they borrowed from Chinese (and, by and large, have the same meaning as in Chinese). They probably account for about 40-50% of the text you will see on any given page of a Japanese book or magazine (or Web site). The kana are phonetic characters. Hiragana is for native Japanese words, and Katakana is used for loan words, most often from English. The two scripts match character for character, with the same pronunciation for corresponding characters. Each character represents a syllable, and, with the exception of the 'n' sound, all end in a vowel. Check out the Romanization of Japanese words, and you'll see that words always end with a vowel or an n. Parenthetically, Mandarin is pretty much the same, except they have a few more consonant endings like 'ng', but never a stopped consonant (k, t, d, b, etc.) In fact, you'll find most native Japanese and Mandarin Chinese speakers will have a lot of trouble with the words stopped consonant ^_^ Romaji (note there's no 'n') is for foreign words to be written in their native script--often names (people's names, brand names), but often just because it looks cool, or there's no way to accurately spell it with the kana. Cordially, Kerry Thompson P.S: I bet you didn't know that written English uses ideograms, just like Chinese. So does German, French, Turkish, Russian, Arabic...almost every written languages use ideograms. [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l Director error code -1101: ANSWER
The only solution we were able to find is to use MX 2004. AND to be sure to use axConvertToFile(soundName, filename, MPEG3/SWA) on a sound file that is _already_ mono OR to use axSetEnvironmentInfo(convertNumChannels, 1) prior to conversion. And that these problems seem, to date, to be Windows-specific and perhaps even sound card specific (Creative SB Live! Value). Thanks for the update Slava. -Sean. [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 PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
