Details

    • Type: Improvement
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Proposal:
      Hide

      option 1:
      get_property always used to retrieve property values even through the value could be changed at runtime.
      get_attribute always used to retrive attribute values at runtime.
      option 2:
      get_property only used to retrive the static value of the property set in the template.
      get_attribute used to retrive both the property and attribute value at the runtime.
      in this option, it also suggests that adding a new keyname "changeable" at the property definition(A.4.4.1).
      changeable no, default=true boolean An option key that declare a property can be changed(true) at the runtime or not(flase)
      if the property is changeable, the user should use get_attribute at any time for retriving its value.
      if the property is unchangeable, the user should use get_property for retriving its value.

      Show
      option 1: get_property always used to retrieve property values even through the value could be changed at runtime. get_attribute always used to retrive attribute values at runtime. option 2: get_property only used to retrive the static value of the property set in the template. get_attribute used to retrive both the property and attribute value at the runtime. in this option, it also suggests that adding a new keyname "changeable" at the property definition(A.4.4.1). changeable no, default=true boolean An option key that declare a property can be changed(true) at the runtime or not(flase) if the property is changeable, the user should use get_attribute at any time for retriving its value. if the property is unchangeable, the user should use get_property for retriving its value.

      Description

      In the wd03-Rew06 document, section 17, it said that "
      It should be noted that the actual port value of the notification_port attribute may or may not be the value 8000 as requested on the property; therefore, any node that is dependent on knowing its actual “runtime” value would use the get_attribute function instead of the get_property function."

      but how could the user know that the value of the property set in the template would be changed at the runtime. what if in this example, user uses get_property function, it will only get the value of "8000" no matter the notification_port changed at runtime, or it can get the actual value?

      do we have an example that the property value should be changed at the runtime even through the value of the property has been set in the template?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              lishitao shitao li
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: