For Windows based dialogs and UIs, the most appropriate choice for the mechanical action of a STOP button would be: a. Switch when pressed. b. Latch when pressed. c. Switch when released. d. Latch when released. e. Switch until released.
For a machine control application, the most appropriate choice for the mechanical action of a STOP button would be: a. Switch when pressed. b. Latch when pressed. c. Switch when released. d. Latch when released. e. Switch until released.
The color of the Call Library Function Node indicates: a. Whether the function uses the C calling convention or the Stdcall (WINAPI) calling convention. b. Whether the function is thread-safe or thread-unsafe. c. Whether the function is executable. d. Whether the function is reentrant.
I think the answer for first question would be "latch when released".This would be because the button will change its value after the dialog box is over once.But same could be accomplished by using "switch when released" because when we press the button on dialog box, the button stays pressed until the appropriate action completes or dialog box completes its action associated with that button and then resets to the off state. Depending upon how we write the program, we can accomplish the same action with both"latch when released" and "switch when released" but correct answer would be (d)latch when released.
The correct answer for the second also depends upon the user as how he wants to design his software and how he wants to use the buttons. But for windows dialog stop button one should use latch action and on machine control applications, one should use switches. But by default anyone should use " switch when released" in this, so correct answer would be (c).
For the third answer, it would be (b): depending upon whether the call library function node thread is safe or not.