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
with the v3 release, mostly when the space is not sufficient, only the first few characters are displayed so sometimes we see identical file name from different images.
The request is to have a better way to handle long file names so that users can easily read the full file names to know which image is which.
We may consider to use tooltip to show the full file name. For example:
Screen.Recording.2022-08-04.at.14.50.04.mov
We may also consider to show first part and last part of the long file name with ... in between like what macOS does.
The text was updated successfully, but these errors were encountered:
@kswang1029@YuHsuan-Hwang:
I would like to discuss with you a bit first before making the first commit to this issue.
According to the description above, I am not sure which part of CARTA should be applied to the new function. Since the "File browser" is already with tooltip to show the file name (see below):
Hence, I assume that the new function should be applied to the "Image List" layer, right? Please let me know if it's not.
I have made a quick modification about it, which is shown below:
Do you think if the format is OK to go? Or should I use the same format of the "File browser"?
user feedback from v3 beta test
Images from the ALMA Science Archive usually have long file names such as
with the v3 release, mostly when the space is not sufficient, only the first few characters are displayed so sometimes we see identical file name from different images.
The request is to have a better way to handle long file names so that users can easily read the full file names to know which image is which.
We may consider to use tooltip to show the full file name. For example:
Screen.Recording.2022-08-04.at.14.50.04.mov
We may also consider to show first part and last part of the long file name with ... in between like what macOS does.
The text was updated successfully, but these errors were encountered: