Closed wkitty42 closed 3 years ago
They are harmless, it it the same issue. But I find it interesting you may have identified what causes them so keep this issue for sure because it points to a cause. It is related to tooltip maybe, those properties look like generic code base, like something a tooltip may invoke. Would be good to report that to dev list and see if we can get some answers,
perhaps @Zaretto knows something about it? i think that's the right person... tagging them here to see before posting to the dev list...
I see that too at the c182s, but otherwise all seems well. The props above are triggering from the tooltip hover-on. I don't know why, however.
There are cases when the error message is given incorrectly because normally you cannot listen to a tied property; except for a few cases where you can.
The idea is that we will add exceptions to the code to mark properties that are tied but can be listened to (such as view-number) to the core to remove the false warnings.
It helps if the model developer can investigate whether the listener works (add a print statement and see if the listener is called) and report any false positives to the devlist and exceptions can be added to the core.
Yeah, you can safely ignore these issues.
These setlisteners are set on line 108 of tooltip.nas: var l = setlistener(p, func { me._updateText(); }); I'm going to close this, the only action to take here is to see if these properties can be marked as an exception; otherwise these are harmless warnings not caused by C172 code.
FG 2019.2.0 i'm seeing the following when i roll over these items and the tool tip pops up... i'm not trying to activate them... only rolling the mouse over them...
maybe these are related to #1281? i dunno... if there's a way to combine the two reports, i don't have a problem with that... these are the only ones i'm seeing and only when i roll over them... i'm in mid-flight when i saw them pop up on my console...
my build data is:
and my c172p is
commit 4cc48b6c7ae2ac47369ebd22ebbd0722cf47d9f2