Xeall Posted August 11, 2013 Report Share Posted August 11, 2013 Hi there, After trying to compile a project I have been working on it suddenly came up with 600+ errors.All of the errors were of the form "'element name' can not have both 'Touch' and 'Hide' linked to the same operand".After looking at a few of the elements affected it was clear that every single element in my project had all of its empty links set to MB 524. Up until a couple of days ago, my project compiled and downloaded successfully.Now there are 3306 instances of MB 524 in my project. For example:The "Links" section on a binary text variable. Before AfterLink: MB 1069 MB 1069Hide: MB 524Disable view: MB 524Marking view: MB 524Legal entry: MB 524Touch: MB 524 I am using VisiLogic Version 9.5.0 Build 0 I am not sure if this is a bug I have found or something I could have caused. Either way, I would appreciate any help figuring out how to remove MB 524 from every link so I can compile my project. (I would prefer not to have to manually remove all 3306 instances) Please let me know if there is any additional information I could provide in resolving this issue. Link to comment Share on other sites More sharing options...
MVP 2014 Simon Posted August 12, 2013 MVP 2014 Report Share Posted August 12, 2013 To ensure a quick response I would recommend emailing the text of your post above to support@unitronics.com Also attach the Visilogic project file to the email if possible. Link to comment Share on other sites More sharing options...
bm_engineering Posted October 30, 2013 Report Share Posted October 30, 2013 This just happened to me, exactly the same way. Every link in every screen object that did not already have a value in it got the same address (mine was MB1020) It was a result of doing a find and replace to multiple MB operands. I sent it to tech support, and they did clean it up for me. However, they never responded to my question of what happened and how to prevent it again. I have since had some additional, but far less catastrophic, problems with operand find and replace. In one case, an MI got replaced by an MB, definitely NOT what I had specified. I believe there is a major issue with the Visilogic find and replace function. Link to comment Share on other sites More sharing options...
AlexUT Posted November 3, 2013 Report Share Posted November 3, 2013 bm_engineering, Please send your original project and explanation of your changes to simulate problem to support@unitronics.com BR. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now