Under what circumstances would/should working on an App in NAB update the VVMTS Maint Timestamp on a Widget in VVWDG100??
We have a few projects where I have assigned Data Source / Widget development to developers relatively new to Valence. And I have been configuring the App myself.
I have been using the Widgets' VVMTS to signal me that someone has made recent changes to a widget that I should review.
Several times, and today was proof positive, I was in NAB working on the App. After completion, I noticed that four (out of about 10) widgets from the app had their timestamps updated, and showed me as the Maint User.
I did nothing to the widgets themselves. I don't remember exactly what I did to those four in the app, but it was either behaviors, or appvar linkage, or both.
Why would/should App maintenance ever update the Widget object at all?
We have a few projects where I have assigned Data Source / Widget development to developers relatively new to Valence. And I have been configuring the App myself.
I have been using the Widgets' VVMTS to signal me that someone has made recent changes to a widget that I should review.
Several times, and today was proof positive, I was in NAB working on the App. After completion, I noticed that four (out of about 10) widgets from the app had their timestamps updated, and showed me as the Maint User.
I did nothing to the widgets themselves. I don't remember exactly what I did to those four in the app, but it was either behaviors, or appvar linkage, or both.
Why would/should App maintenance ever update the Widget object at all?
Comment