jzoller Posted September 1, 2009 Report Share Posted September 1, 2009 Open Query XML Document for Multiple Nodes.vi (from the example finder), and delete the error line immediately after the for loop. Save what you're working on... and run the XML VI. LV apparently fishes around for a moment, then goes away. Joe Z. x-post to http://forums.ni.com/ni/board/message?board.id=170&message.id=437600 Quote Link to comment
Kurt Friday Posted September 2, 2009 Report Share Posted September 2, 2009 Open Query XML Document for Multiple Nodes.vi (from the example finder), and delete the error line immediately after the for loop. Save what you're working on... and run the XML VI. LV apparently fishes around for a moment, then goes away. Joe Z. x-post to http://forums.ni.com...ssage.id=437600 I think what is happening is that by deleting the error wire you break the dataflow. So the order of operations may be Load XML String, Get All Matched Nodes, Close then run invoke node Get XML on the Node Result Array which will now be invalid because you closed the main ref. Why it's crashing LabVIEW I don't know. Quote Link to comment
John Lokanis Posted September 2, 2009 Report Share Posted September 2, 2009 Closing the parent node invalidates all the children nodes. But, it should error, not crash. Quote Link to comment
Adam Kemp Posted September 3, 2009 Report Share Posted September 3, 2009 Open Query XML Document for Multiple Nodes.vi (from the example finder), and delete the error line immediately after the for loop. Save what you're working on... and run the XML VI. LV apparently fishes around for a moment, then goes away. Joe Z. x-post to http://forums.ni.com...ssage.id=437600 If you haven't already done so, please report this as a bug. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.