SplashStack1 is the first version of the SplashStack Main stack (one file only).

How do I install the first version of the of the SplashStack1 Main stack?

• Return to the Download Page, click "Download" - Download is extremely rapid !
  
• Locate the downloaded ZIP file, which is represented by a single file called "SplashStack1.zip".
  Depending on your computer, Operating System and System Parameters, it may be on the deskTop, in the Downloads Folder, in the Documents Folder, etc.
  
• Unzip the downloaded file. Depending on your computer, Operating System and Browser Preferences, a double-click will normally launch the unZip function.
  
  On Mac OSX Systems, the unzip function is automatic, and will create the unzipped "SplashStack1.rev stack".
  
  If no UnZip application is apparent on your computer, you may download the 7-zip Expander which will do the job admirably.
  7-zip exists for Mac and PC platforms. 7-zip may exist on your PC, if so use this !
  
  
• The unZip function will create a single file called SplashStack1.rev.
  
  Specifications of this stack
  
  SplashStack1 is a standalone LiveCode Stack (.app or .exe). This is my first version. It handles Single or Multiple stack targets of Called Stacks.
  SplashStack1 calls another stack (.rev), in such a manner that modifications to the called stack will be saved on exit to the application.
  SplashStack1 builds a list of all file names within the same folder as itself. After eliminating all spurious names from the folder contents list,
  if there is only one stack left, go to it (Call xxxx) . If there are more, put all of the names in a list and let the user decide, by selecting the target !
  
  The "OpenStack" script not only prepares the name of the "Called" stack, and goes to it, but allocates values to global variables for possible later use.
  Depending on the scope of the "Called" stack, the use of external files, such as "Photos", "Audio", "Video", "Data", "PDF" and "Print" files may exist
  in folders of that name. The SplashStack Stack sets up all of these pointers in global variables, and each stack uses the pointers that it requires.