Announcement
Collapse
No announcement yet.
using [axshockwaveflash1] asking for enable javascript
Collapse
X
-
Originally posted by butteYou might try checking the two sets of flash code (within the game and within the file that loads it, if both) to see that you've not only called it but used whatever syntax it thinks is correct. In using flash for esri displays, for example, either of the two can "go south" when fired.
Comment
-
Originally posted by butteYou might try checking the two sets of flash code (within the game and within the file that loads it, if both) to see that you've not only called it but used whatever syntax it thinks is correct. In using flash for esri displays, for example, either of the two can "go south" when fired.
** iam using Vb.net
Comment
-
Originally posted by butte1/ Generally, right-click an executable or other *compiled* file and look at its properties. Version, build, etc., usually wind up in the right tab of properties.
2/ Generally, open an *uncompiled* file (.xml, .gpx, etc.) with a text editor and read the first several lines. Version, etc., usually wind up near the top.
why i do this ?
Comment
-
Originally posted by electrons View Posthmmm, i forget to tell you , i load SWF File from URLOriginally posted by electrons View PostI am sorry for any misunderstanding , I had confused!! why i do this ?
The reason for routinely asking for Versions is that those often give clues as to what is going on. In WW the versions and builds probably matter. In Vb.net and flash, the versions and builds might matter. The operating system itself may matter in conjunction with (paired with) a particular version of JavaScript syntax (its standards slowly change). The 1/ and 2/ are merely ways to get at the versions and builds.
Also try proofreading your code. If you got it somewhere else, proofread it anyway (*very often* the freeware code in made available in boxes on code-source websites has built-in minor typographical or other basic errors in it). Ensure that every line lands properly (e.g., ";"), and that every brace ("{", "}") is in the right sequence and has a mate (they open and close segments of execution). If the processor (your cpu chip) receives what it thinks is gibberish, it won't do what you expected; even just *one* too few or too many of those little punctuation marks (";", "{", "}") can make or break otherwise good code.
Comment
-
Make use of browser developer tools to debug JavaScript code and Buckshot Roulette pc inspect network requests. You can use the console to view error messages and debug statements, as well as inspect the network tab to see if there are any failed requests related to the Flash content.
Comment
Comment