asbo Posted October 1, 2009 Report Share Posted October 1, 2009 The way I would envision this to work would be if you select to ignore incoming errors the error input would change from black to red. I don't think that's enough of a difference, personally - what about a strike or a slash through the "!?" instead of a color difference? Quote Link to comment
Mark Yedinak Posted October 1, 2009 Report Share Posted October 1, 2009 I don't think that's enough of a difference, personally - what about a strike or a slash through the "!?" instead of a color difference? That would work too. I was basically suggesting the color to remain consistent with the current "Ignore Errors inside Node". Quote Link to comment
Gary Rubin Posted October 1, 2009 Report Share Posted October 1, 2009 And as long as the according control is set to not operate synchronously, updating a local or terminal will NOT wait until the new value is updated on screen. It will simply drop the new value into a buffer of that control and go on. The UI thread periodically will check for such controls that need an update and redraw them. Controls (vs. indicators) also have a synchronous/asynchronous setting, but they have to be read with every loop iteration, don't they? Or do they work the same way as asynchronous indicators, where the code will "catch" a change in asynchronous control status whenever it gets around to it? I'm trying to figure out if my processing loop that contains a bunch of controls would run more efficiently if I moved those controls out to a slower loop and passed the results into the processing loop using queues. Quote Link to comment
gb119 Posted October 1, 2009 Report Share Posted October 1, 2009 So the task for someone skilled (or who wants to be skilled) in XNodes is: create a local variable with error cluster terminals Pretty sure it can't be done - a local variable has to sit on the block diagram of the vi which owns the control. I'm not sure exactly which block diagram an XNode scripts its contents onto, but I'l fairly sure it isn't the parent diagram of the XNode itself. That is of course the main advantage of property nodes over local variables - it allows sub-vis to manipulate the controls of the caller (which of course is a disaster unless you're doing UI stuff....) Quote Link to comment
asbo Posted October 1, 2009 Report Share Posted October 1, 2009 Trying to run an error wire through a local is would just be unnatural looking anyway... the flat sequence structure once again finds purpose. Quote Link to comment
crelf Posted March 17, 2010 Report Share Posted March 17, 2010 Trying to run an error wire through a local is would just be unnatural looking anyway... the flat sequence structure once again finds purpose. I don't agree - shared variables have error terminals, and they look fine... 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.