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
Would shrink (or grow) TB so that it is neatly the size of the text.
(That's an oversimplification as there are issues with margins and baselines etc -- but it's a useful minimum starting point for boxes that resize to fit their text content. And, without useful output from SIZE-TEXT it not obvious how to accurately resize boxes - or change font sizes - to fit text content).
Actual behavior
SIZE-TEXT in Red always seems to treat the text as being on one line, so with the above example:
SIZE-TEXT tb
== 119x17 ;; almost always x17, except where we erratically get 0x0 under unreproducible conditions
In R2 the same result is more what we'd expect given the default font size, and text wrapping.
== 16x228
I would not expect exactly the same result from Red - its compositing is bound to be different. But I'd expect sometime close.
Expected behavior
Would expect it to return the "bounding box" for the text contained with in it - so, for example:
Would shrink (or grow) TB so that it is neatly the size of the text.
(That's an oversimplification as there are issues with margins and baselines etc -- but it's a useful minimum starting point for boxes that resize to fit their text content. And, without useful output from SIZE-TEXT it not obvious how to accurately resize boxes - or change font sizes - to fit text content).
Actual behavior
SIZE-TEXT in Red always seems to treat the text as being on one line, so with the above example:
In R2 the same result is more what we'd expect given the default font size, and text wrapping.
I would not expect exactly the same result from Red - its compositing is bound to be different. But I'd expect sometime close.
Steps to reproduce the problem
Red and platform version
RED: [ branch: "master" tag: #v0.6.3 ahead: 1046 date: 26-Sep-2018/19:44:03 commit: #47c6fed063e376a06d6e5ba85889c48b3c5c3434 ]
PLATFORM: [ name: "Windows 10" OS: 'Windows arch: 'x86-64 version: 10.0.0 build: 17134 ]
The text was updated successfully, but these errors were encountered: