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

Details pane in Publish UI : in Substance Painter, instance names are cut #1097

Open
2 tasks done
alainxi opened this issue Jan 22, 2025 · 7 comments
Open
2 tasks done
Labels
type: bug Something isn't working

Comments

@alainxi
Copy link

alainxi commented Jan 22, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior:

After having published images from Substance Painter, the Details pane of the Publish UI shows the instances on the left column.
But those instances are cut, and you can't see the ending of the names, because that column is not resizable.

So, it's difficult to know what we select, we need to inspect the right pane : non-technical users are forced to read dozens of lines in the right pane, this is cumbersome.

Image

Expected Behavior:

The left-most column of the Publish's Detail pane should become one of those :

  • Larger.
  • Auto-adapt to the instance name length.
  • Resizable.

Version

1.0.14

What platform you are running on?

Windows

Steps To Reproduce:

Publish a texture set from Substance Painter.
Open the Detail pane of the Publish UI.

Are there any labels you wish to add?

  • I have added the relevant labels to the bug report.

Relevant log output:

Additional context:

No response

@alainxi alainxi added the type: bug Something isn't working label Jan 22, 2025
@BigRoy
Copy link
Collaborator

BigRoy commented Jan 22, 2025

A simple workaround I use for this. Is "pop off" the logs panel right hand side, there's a button for it. When doing that the remainder UI is for just the two left columns and you have plenty of width.

However, if this is a UI issue - it should maybe be on ayon-core?

@alainxi
Copy link
Author

alainxi commented Jan 22, 2025

This report is already on ayon-core ;-)
I mentioned Substance Painter as an example, because it has long instance names, but I guess the same problem can be found on other DCCs.

Thanks for the workaround.
It is almost a weird one ;-) so artists will forget about it, but it works, thanks !

@BigRoy
Copy link
Collaborator

BigRoy commented Jan 22, 2025

This report is already on ayon-core ;-)

Came in late in the office today and it seems the lack of coffee this morning has this effect on me. :D Sorry about that.

@iLLiCiTiT any ideas from a Qt perspective what could be an effective solution here?

@iLLiCiTiT
Copy link
Member

Anything can be done, UX is the question...

@BigRoy
Copy link
Collaborator

BigRoy commented Jan 22, 2025

I think even showing the full name on hover (e.g. tooltip) could help for very long names.
But making the left section resizable could also help out like @alainxi described.

@alainxi
Copy link
Author

alainxi commented Jan 24, 2025

In the publisher UI, the left column of the Details pane is not the only one that would benefit from allowing long lines of text.

In the Report pane, the middle column contains the logs, but they are heavily cut if the lines are too long.
There are 2 cases :

  • The log lines are too long because there are a lot of words : no problem, there is already an automated carriage return 👍
  • The log lines are too long because there is a word that is too long (for example a file path). You cannot read it, it is cut 👎

My current workaround, when I write a custom validator, is to detect long words (file paths), and to cut them in several parts, separated by a "..." string.
It is not ideal, because a user cannot easilly cut and paste that path. Here is what I get :

Image

With a scrollbar it would be a lot better.

@iLLiCiTiT
Copy link
Member

This should fix logs issue on report page #1104

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants