I am having major problems trying to get what I want, which is a thin strip if text rotated 90 degrees alongside my main UI… Think of a tab on a manilla folder.
It seems that the layout options do not respect transform, or at least not rotation, because the layout sizing, everything remains based on the un-rotated widget.
This means silly things like if you want a tall and thin strip of 90 degree text you can’t because the original layout needs to be wide enough to accommodate the PRE rotated text.
Otherwise, if the pre-rotated layout isn’t wide enough you end up with the text being cut off.
So then I tried making it as a separate element not part of my master layout. I had slightly better success, except once you rotate something, its sizing handles remain as before the rotation as well.
And then I found that when I panned my around my canvas, the layout would suddenly get cut off. Here you can see that the handles for my widget (pre-rotation of course) are close to the edge of the view-port. In this image the whole thing is properly visible.
In this next image I have simply panned the view-port over so that the transform handles are cut off, and you can see what happens to the post-rotated layout. It gets cut off too!
After looking over your post I was able to find that this is a known issue (UE-4659) and that it has been submitted to our developers for further consideration. Thank you for your information and time.
You could place the text block somewhere that it fits completely and then use the Translation settings to move the text into position. This would leave the bounding box in a place that it doesn’t clip. WARNING: this means that the widget will no longer clip with any other edges.
I went ahead and double checked the status of this issue. The the status has not been changed. The issues that take priority are those that cause crashes, prevent users from gaining access to the engine, or that are show stoppers. However, I will bump up the community interest for this issue.
I went ahead and double checked on this issue for you. It appears that you are correct. This issue’s status has not been updated to fixed as of yet. However, I went ahead and bumped up the community interest for this issue. Thank you for you time and information.
It would be really awesome if people who are experiencing this problem could upvote the issue in the issue tracker to help let Unreal know that we’d love it fixed!
