Skip to content
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

Open
SRM256 opened this issue Feb 25, 2021 · 5 comments
Open

Caraya panel problems #126

SRM256 opened this issue Feb 25, 2021 · 5 comments
Labels

Comments

@SRM256
Copy link
Contributor

SRM256 commented Feb 25, 2021

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.

@francois-normandin
Copy link
Collaborator

It's called Process.vi.
You'll find it under Caraya.lvlib:Basic Test Manager.lvclass namespace.

@francois-normandin
Copy link
Collaborator

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.

@SRM256
Copy link
Contributor Author

SRM256 commented Feb 26, 2021 via email

@SRM256
Copy link
Contributor Author

SRM256 commented Feb 26, 2021

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.

@francois-normandin
Copy link
Collaborator

francois-normandin commented Feb 27, 2021

I re-read issue #96 and it seems to be related to the same root cause.
Referencing this here for future investigation in context of both reports.
(Not marking as duplicate as there might be similarities but not a complete overlap)

@francois-normandin francois-normandin modified the milestone: 1.2 Jul 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants