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
{{ message }}
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.
In the graph window, when I hover on some elements, the tool sometimes displays a popup window with information. For example, a full path of a file.
The issue is that the width of this popup window is not wide enough to show the complete full path, only the beginning is shown and a scroll bar is added. This is annoying as I need to see part of the path not directly shown.
Currently this popup window seems to limit its width to about one third of my monitor width. This seems counter productive.
I would like Sourcetrail to have an option to make this window much wider and to show the complete full path directly (as much as possible).
Thanks
(I am using Version 2018.2.19-64 bit on Centos)
The text was updated successfully, but these errors were encountered:
It would seem easier to allow for wider hover-popup windows, and other types of data would also benefit (not just file path). I have seen class or method info in a hover-window with a scroll-bar for no real good reason.
In the graph window, when I hover on some elements, the tool sometimes displays a popup window with information. For example, a full path of a file.
The issue is that the width of this popup window is not wide enough to show the complete full path, only the beginning is shown and a scroll bar is added. This is annoying as I need to see part of the path not directly shown.
Currently this popup window seems to limit its width to about one third of my monitor width. This seems counter productive.
I would like Sourcetrail to have an option to make this window much wider and to show the complete full path directly (as much as possible).
Thanks
(I am using Version 2018.2.19-64 bit on Centos)
The text was updated successfully, but these errors were encountered: