Menu
▾
▴
#1201 Private variables mismatched between families and objects
Working with my game, I found a fairly irritating error...
I have an object that is part of a family. When Its PV (Destroy) is set to one, it is supposed to be destroyed.
However, I set the Family's Destroy PV to 1 but nothing happens.
Upon debugging the app, I discover that it is actually adding it to a DIFFERENT PV for some reason (Power).
This is how the variable list is in the object:
ID
Power
Destroy
...
And here's the same list, but from the classes PVs:
Power
Destroy
Blah
...
ID
So when I set the Family's 'Destroy' to 1, it is actually setting the Object's 'Power' to one.
More info on the object in question:
It IS the ONLY object in the family, however, it wasn't the first. I originally created a previous object for that family and assigned the family to both objects (Object A and Object B, respectively).
I deleted Object A, no longer needing it, and then added new variables to Object B, and now the variables aren't corresponding correctly.
I would give a .cap, but for the LIFE of me I can't reproduce it. Ive attempted recreating the error several times.
I will keep trying and will send a .cap as soon as I can, if able.
Ok, Ive seem to have come across it again. This bug is CRIPPLING. When It occurs you simply CANNOT go on untill you:
Delete the family.
Re-code EVERYTHING with a different family.
And if only seems to target larger projects.
Also, good news: I'm almost finished preparing a .cap for it, and I'll upload it within 24 hours.
Follow instructions in comment [Cap1 Instructions]
[Cap1 Instructions]
1. Run the cap in Debug Mode
2. Pressing space is meant to set the PV 'Controller' to 1337, however, it is assigning that value to a different PV.
I've come across this problem as well, if not every member has the exact set of pv's on a larger project, it will start messing up assignments and conditions
The PV index in the family seems to be out of order. Until the cause is found and it is fixed, here is a workaround:
Open up the action and right click on the text "private variable" and select use expression.
The value in this case will be 57, erase that and type in the name of the PV you want to use and put it in quotes. Be sure it is spelled correctly or it will cause a crash.
I added this when I was fixing PV access from python. :-)
Upon further investigation most of the variables seem to be in the correct location, but after a point they are one off.
If you open "manage families" remove the "STAT_Speed" PV from the family then re-add it the problem seems to be resolved.