I have 4 Av objects with initial values assigned via the InitialValue parameter. When I start up the Runtime something strange happens.

According to my seetings, what I expect is this:
[code:1]Av object index initial value

---

Av1 0 1
Av2 1 2
Av3 2 3
Av4 3 4
[/code:1]

But what I get is this:
[code:1]Av object index initial value

---

Av1 0 1
Av2 1 2
Av3 2 2
Av4 3 4
[/code:1]

The initial value of the second Av object is used to initialise the third Av object as well.
I tried changing the order of the Av objects, but it's always the third one that gets initialised with the value of the second one.

Is this a bug? Any idea for a workaround?

Ondrej

I did some more testing with 8 Av objects and this is what I found:

[code:1]Av object index initial value (expected)

---

Av1 0 1 (1)
Av2 1 2 (2)
Av3 2 2 (3) <-
Av4 3 4 (4)
Av5 4 3 (5) <-
Av6 5 6 (6)
Av7 6 4 (7) <-
Av4 7 8 (8)
[/code:1]

So it looks like there is some misalignment of the index the initial value is taken from.

Ondrej

Hello Ondrej,

Which version are you running ?

This was a V4.7.0-1 bug and should have been fixed in V4.7.0-2.

The workaround is to use the setvalp command in the pwrp_alias file to set the values.

/Claes

Hi Claes,

I am still using the first 4.7 release, so that's why I get this bug. I guess I should update my development environment

The workaround I used is to insert dummy Av objects at the positions that get the wrong initial values.

Thanks, Ondrej