Thatâs why I had to use the decorator above - even calling self.callback isnât a PyFunction, itâs a PålassMethod or something similar, so the strict cast we have in our code wonât work. Tagnotate tags Patch#Thereâs not really any great ways around that, until/unless we patch the method internally. Unfortunately, the writeAsync callback argument isnât defined very well - trying anything fancy will probably lead to : Cannot coerce value '' into type: class. I was able to get your example working with some modifications: tagPath = "alarm" Intuition: user history is necessary for accurate kernel prediction. I think you already had a callBack variable in scope - were you testing in the script console? As is, neither of your examples will actually run - tagPath, state, and callback are not defined in the scope of the tagWrite function. (,, callback)Ä®xplicitly I need a completely different name for the callback, because its on a class that may have a handful of different callbacks after tag writes. tag tagwriten //trim(tag)//n the number of spaces.(,, callBack)Ä«ut this does not tagPath = "Lines/Icing/Equipment/Mixer/State" Tags are represented in IOTK binary files directly as character strings. This works: tagPath = "Lines/Icing/Equipment/Mixer/State" TagWrite is set up through a template using English-type tokens. Is this a bug, or is there a reason that the callback function specifically needs to be named and typed that way? It's available on several from one tagging llne oubllcatlons. Whenever I try to execute a callback with a name other than callBack (I cant even use callback) it fails showing that the global name is not defined.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |