Specific case Z layer ordering is a key feature with art engine but is currently broken. Users defining a layer such as "z-10,Cozy Jacket" should evaluate that "Cozy Jacket" would move the item to z index -10 despite its parents structure. The offending method is parseZIndex within src/main.js which attempts to extract and parse an in value with z# Ex. Although "z10," is valid it is fed into theparseInt with z still prepended such as z10 rather than 10.
The function will always evaluate to null. This fix allows for the 3 possible cases below as described in the docs:
Case 1: User defines no override for Cozy Jacket which uses default value from config.js layerConfigurations[]Directory Input:
- Clothing
- Cozy Jacket
Output:
Name: Cozy Jacket
Z Order: NULL (no override. default value used instead)
Case 2: User defines override for Cozy Jacket at -10Directory Input:
- Clothing
- z-10,Cozy Jacket
Output:
Name: Cozy Jacket
Z Order: -10
Case 3: User defines override for Cozy Jacket at 10Directory Input:
Specific case Z layer ordering is a key feature with art engine but is currently broken. Users defining a layer such as "z-10,Cozy Jacket" should evaluate that "Cozy Jacket" would move the item to z index
-10
despite its parents structure. The offending method isparseZIndex
withinsrc/main.js
which attempts to extract and parse an in value with z# Ex. Although "z10," is valid it is fed into theparseInt
with z still prepended such asz10
rather than10
.The function will always evaluate to null. This fix allows for the 3 possible cases below as described in the docs:
Case 1: User defines no override for Cozy Jacket which uses default value from config.js layerConfigurations[] Directory Input:
Output:
Case 2: User defines override for Cozy Jacket at -10 Directory Input:
Output:
Case 3: User defines override for Cozy Jacket at 10 Directory Input:
Output: