You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I noticed this happens to me on my ubuntu laptop, but not on the team's windows DS,
on the NT data table preview on the side, all of the topic names are getting stacked on top of each other and makes it unreadable
To Reproduce
Steps to reproduce the behavior:
Open Advantage Scope through the Start Tool menu on WPILib vscode
Connect to the robot / sim / log file
View the side preview of the NT table
Expected behavior
All of the topic names are getting stacked on top of each other.
Screenshots
Version (required):
Version: 3.2.1
Distributor: WPILib
Platform: linux-x64
Build Date: 3/13/2024, 22:19:40 UTC
Electron: 26.2.1
Chromium: 116.0.5845.188
Node: 18.16.1
The text was updated successfully, but these errors were encountered:
This looks like the same problem as #99, which was the result of Intel driver issues. We can potentially switch Electron/Chromium versions if there have been related changes, but it seems like this is essentially a Chromium/Intel bug.
This looks like the same problem as #99, which was the result of Intel driver issues. We can potentially switch Electron/Chromium versions if there have been related changes, but it seems like this is essentially a Chromium/Intel bug.
Describe the bug
I noticed this happens to me on my ubuntu laptop, but not on the team's windows DS,
on the NT data table preview on the side, all of the topic names are getting stacked on top of each other and makes it unreadable
To Reproduce
Steps to reproduce the behavior:
Start Tool
menu on WPILib vscodeExpected behavior
All of the topic names are getting stacked on top of each other.
Screenshots
Version (required):
Version: 3.2.1
Distributor: WPILib
Platform: linux-x64
Build Date: 3/13/2024, 22:19:40 UTC
Electron: 26.2.1
Chromium: 116.0.5845.188
Node: 18.16.1
The text was updated successfully, but these errors were encountered: