-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Caraya panel problems #126
Comments
It's called Process.vi. |
This feels like a bug. Can you comment whether or not it is impossible to recall it to open from either project or both? Gut feeling: the assertion factory is a singleton. Tests are performed in a project's namespace but interactive UI is tied to the other one, so the tests are run and sent to an uninitialized engine. I'm not certain (I might be totally wrong about this), but I think the first assert event should trigger the interactive UI to be shown. If the event is not received, that would explain the symptom you describe. |
Oh, it's definitely a bug. Getting the name of the dialog is just so I have
a workaround. Thank you for the information.
|
I only have tests in one of the two projects (it's a client/server setup, and I'm only testing one side). Caraya only exists in one of the two projects. Nothing would trigger it to open in the other project. |
I re-read issue #96 and it seems to be related to the same root cause. |
What is the name of the Caraya dialog VI? I need to be able to find it in the project to manually open it, and it doesn't seem to be named anything like "Dialog.vi".
Why do I have to manually open it? Because I have two projects open. And if you have two projects open, you must be very careful to never close the Caraya window after it opens the first time because it will never come back.
The text was updated successfully, but these errors were encountered: