Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugfix: Node.set_value() does not work with enumerations #888

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Bugfix: Node.set_value() does not work with enumerations #888

wants to merge 2 commits into from

Commits on Sep 9, 2019

  1. Bugfix: Node.set_value() does not work with enumerations

    If a client tries to set a enum variable without explicitly force the data type it becomes implicit converted to a ua.Variant.Int64. The server expects an Int32 for an enum value. This is why set_value() crashes if you try to set an enum value using a integer literal like "set_value(2)".
    
    The enumeration seems to need a special treadment at this point. See ua_utils.py def data_type_to_variant_type().
    
    If no data type was given in method set_value(), this change checks the data type of the node object and automatically converts the value argument to the correct target data type of the server.
    MarcoH82 authored Sep 9, 2019
    Configuration menu
    Copy the full SHA
    66c0fd4 View commit details
    Browse the repository at this point in the history
  2. Accidentally double-added line removed

    MarcoH82 authored Sep 9, 2019
    Configuration menu
    Copy the full SHA
    f30edfd View commit details
    Browse the repository at this point in the history