Expand TextMorph to encompass entire string?

Any suggestions?

[Ron Teitelbaum] Hi John-Reed,

There are a number of method available to you on TextMorph.  Browse TextMorph and press the instVars button.  Select wrapFlag to see Accesses to that.  In general the TextMorph has methods that should update the text to wrap the contents when you update or add text.  You can also probably wrap the text manually (calling the wrap method yourself) as you add it depending on the width of the string you are adding.  Also look for how to set the height of the row, and set that based on the results of the number of lines returned from the wrapping times the font height + some bounds between lines.  It may do that already in some cases (not reading the code so not sure).  In general you need some sort of compose method that looks for all the variables.  The length of the string, the width of the column, the font size, and it should trim the strings based on width to rows (possibly in something like a paragraph), and set the height of the row to accommodate the string, and possibly add a scroll bar if it doesn’t fit.  (remember to add the width of the scroll bar in your compose method).  That method needs to be called whenever something changes, like when the component is resized or new text is added or removed.

I would think that there is already a method that does all this so start with the wrap flag method and see how others are doing the same thing.

Not sure if that is much help but you never know!

All the best,

Ron Teitelbaum  

jrm

I have resolved the issue, by trying a lot of different, minor modifications to my methods; 59 versions of the most problematic one!

[Ron Teitelbaum] Excellent I’m glad you figured it out!

The answer to my question seems to be rooted in my choice of a #layoutPolicy: ( btw, what is the appropriate use of the # sign when talking about Smalltalk code?

[Ron Teitelbaum] # followed by some string literal indicates a symbol which are great for things like parameters (#spaceFill) which are easy to compare.  In the context of discussing code in an email I will sometimes use #foo to indicate a method name but I’m also likely to use  Object >> foo or anObject >> foo because of how the debugger shows messages.  Had you not asked the question “my choice of a #layoutPolicy: “ was perfectly understandable.

) and specifying the height of containing morph based on the height of the largest contained morph.

Comment to anyone reading this in search of information, be patient and confident of finding a solution. Keep searching for answers and asking questions. 

---- begin