Difference between revisions of "Amira Quirks"

From CRIPTWiki
Jump to: navigation, search
(Created page with '==Root Directory Saving Problem== You SHOULD NOT save any network under the root directory of a drive. For example, if your USB drive is located at E:\ do not save at E:\ direc...')
 
Line 1: Line 1:
 
==Root Directory Saving Problem==
 
==Root Directory Saving Problem==
You SHOULD NOT save any network under the root directory of a drive.  
+
<span style="color:red">You SHOULD NOT save any network under the root directory of a drive. </span>
  
 
For example, if your USB drive is located at E:\ do not save at E:\ directly but in a folder beneath E:\ like E:\Amira\ or any other name.
 
For example, if your USB drive is located at E:\ do not save at E:\ directly but in a folder beneath E:\ like E:\Amira\ or any other name.
  
Why is this happening?  
+
 
 +
===Why is this happening? ===
 +
 
 
You need to understand [[Amira network structure]] first.  
 
You need to understand [[Amira network structure]] first.  
  
...so what happen if you do save it there?
+
===...so what happen if you do save it there?===
Well, when you save at NON-ROOT directory, you get correct relative referencing of the .hx network.
+
Eg. .hx will load \a.am \b.am \c.am with REFERENCE relative to the .hx file PROPERLY.
+
  
However, if you save at the ROOT directory, you will only get PRECISE definition of the .hx network.
+
Let's say you have a network called "test.hx" that loads three files a.am, b.am, c.am that are located in the data directory of the same network ("test-files" folder)
Eg. .hx will now attempt to load C:\a.am, C:\b.am, C:\c.am with ABSOLUTE path definition and result in file problem once you copy the networks around since it will always look for the file in those SPECIFIC locations.
+
  
 +
Well, when you save at NON-ROOT directory, you get correct relative referencing of the .hx network by loading the data modules at the proper RELATIVE locations.
 +
Eg. "test.hx" will load "test-files\a.am" "test-files\b.am" "test-files\c.am" with REFERENCE relative to the .hx file location PROPERLY.
  
 +
However, if you save at the ROOT directory, you will only get PRECISE definition of the .hx network.
 +
Eg. "test.hx" will now attempt to load "C:\test-files\a.am",  "C:\test-files\b.am", "C:\test-files\c.am" with ABSOLUTE path definition and result in file problem once you copy the networks around since it will always look for the file in those SPECIFIC locations (C:\test-files\).
  
 +
==Save Network==
 +
Another key issue you need to be careful is how you save your network.
 +
<span style="color:red">ALWAYS save as "Pack and Go".</span>
 
[[Category:Amira]]
 
[[Category:Amira]]

Revision as of 15:39, 8 May 2009

Root Directory Saving Problem

You SHOULD NOT save any network under the root directory of a drive.

For example, if your USB drive is located at E:\ do not save at E:\ directly but in a folder beneath E:\ like E:\Amira\ or any other name.


Why is this happening?

You need to understand Amira network structure first.

...so what happen if you do save it there?

Let's say you have a network called "test.hx" that loads three files a.am, b.am, c.am that are located in the data directory of the same network ("test-files" folder)

Well, when you save at NON-ROOT directory, you get correct relative referencing of the .hx network by loading the data modules at the proper RELATIVE locations. Eg. "test.hx" will load "test-files\a.am" "test-files\b.am" "test-files\c.am" with REFERENCE relative to the .hx file location PROPERLY.

However, if you save at the ROOT directory, you will only get PRECISE definition of the .hx network. Eg. "test.hx" will now attempt to load "C:\test-files\a.am", "C:\test-files\b.am", "C:\test-files\c.am" with ABSOLUTE path definition and result in file problem once you copy the networks around since it will always look for the file in those SPECIFIC locations (C:\test-files\).

Save Network

Another key issue you need to be careful is how you save your network. ALWAYS save as "Pack and Go".