|
|
 Bugs with properties
| Issue Type: |
Status: |
Priority: |
Date Submitted: |
Votes: |
| Bug |
Open |
Medium |
Fri 4th Nov 2011 |
2 votes
 |
| |
| Found in version: |
Last Updated: |
Completed in version: |
Date Completed: |
Track Changes: |
| 5.0.21 |
Wed 6th Feb 2013 |
|
|
Log In |
| |
| | Fri 4th Nov 2011 16:17 |
Some issues with the way Adrift currently handles properties. In some cases Adrift seems to evaluate functions too late, resulting in the following scenarios, and possibly others:
- If you use an '%object%' reference in the 'PropertyValue' function and then store the result in a property. When you refer to the property later, It fails to output anything with a cannot find '%object1%' error.
- I set up a task that refers to an array index using a variable and stores the result in a property. It then modifies said variable and reuses it to refer to the same array and store the result in a second property. However, the result of the second reference appears in both properties.
Link to discussion thread: http://forum.adrift.co/viewtopic.php?f=14&t=7580 |
| |
| | Wed 6th Feb 2013 18:41 |
| The first example above now works (with v29) if you use the object orientated style syntax, but still fails if you use %PropertyValue[]%. |
|
