Adding instrument to TUI, Panel Frozen?

I was able to do this a while ago, but can’t seem to get it to work any longer.
Here are the steps I’ve used previously to add a new Instrument in TUI, but can’t now, the GUI seems stuck and I have to shut down my docker container:

  1. Started with an OpenTap docker container and installed the KS IO Lib and TUI
  2. Run: tap tui
  3. In the TUI, click Bench, then Instruments, which brings up the new Instruments panel
  4. Click the [+] entry, which brings up a choice of Generic SCPI Instrument and Demo
  5. Highlight the Generic SCPI Instrument and click enter key, this brings up the Instruments panel again, whereas before it would bring up an Instrument editor panel
    So the GUI/TUI now looks like this and the [+] entry is no longer active (or it won’t accept mouse clicks or enter key or space key).
    Any idea what might be going on? Again, at one time this week it was working in that I could add a real SCPI instrument with a TCP SCPI address and create a test step to try to execute a command against it. But now I’m stuck in the mud for the last 8 or 9 hours.

UPDATE:
I clicked the on the panel and two new SCPI entries appeared, but again I can’t tell consistently how or when the panel will populate after clicking the [+] entry:

Hey @mescgroup

I have tried reproducing your issues, but without success.

But I did find some focus issues, where you could inadvertently be clicking views that are not in focus. This could cause the behavior you saw with clicking the panel again, which changes the focus.

I have pushed a new version, let me know if that helps.

@stefan.holst , I couldn’t get the PullLatest branch to build (see error below). Do I have to have the entire opentap source downloaded in order to build just the tui project?

I recorded the problem I was having in a movie file if that is of any help, though it doesn’t look like I can upload mp4 files directly to the forum.

After running through the usecase a couple of times, it does get into a state whereby if I walk away for a few minutes and then come back, the new SCPI instrument (actually several) appear in the panel.

Here is the error I get when trying to build the branch:

root@docker-desktop:/gitprojects/opentap-tui# git checkout PullLatest
Branch 'PullLatest' set up to track remote branch 'PullLatest' from 'origin'.
Switched to a new branch 'PullLatest'
root@docker-desktop:/gitprojects/opentap-tui# dotnet build

Welcome to .NET Core!
---------------------
Learn more about .NET Core: https://aka.ms/dotnet-docs
Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli-docs

Telemetry
---------
The .NET Core tools collect usage data in order to help us improve your experience. It is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.

Read more about .NET Core CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry

ASP.NET Core
------------
Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.
Microsoft (R) Build Engine version 16.2.37902+b5aaefc9f for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

/usr/share/dotnet/sdk/2.1.818/NuGet.targets(267,5): error MSB3202: The project file "/gitprojects/opentap-tui/gui.cs/Terminal.Gui/Terminal.Gui.csproj" was not found. [/gitprojects/opentap-tui/OpenTAP.TUI.sln]

Build FAILED.

/usr/share/dotnet/sdk/2.1.818/NuGet.targets(267,5): error MSB3202: The project file "/gitprojects/opentap-tui/gui.cs/Terminal.Gui/Terminal.Gui.csproj" was not found. [/gitprojects/opentap-tui/OpenTAP.TUI.sln]
    0 Warning(s)
    1 Error(s)

Hey @mescgroup sorry for the late response. Are you still having these issues? I have made a lot of commits since, so this should be fixed now.

2 Likes

No, but thanks for checking.

1 Like