I’m having an annoying problem. When typing text into an inflow item, the text I’m typing isn’t visible once I pass the end of the current text line. The curser moves down, and I can continue to type, but I can’t see the text. If I command-tab to a different program and back, the screen refreshes, and I can see what was previously hidden. When I reach the end of the that line and the next line starts, it’s the same thing. (There is a graphic footer image below the text, one that gets pushed down as the text area expands.) Is this a Freeway issue, a RAM issue…? Any thoughts?
I’ve seen this in Freeway as well. When I do see it, scrolling that part of the page off screen and back again is enough to jog its memory and repaint the text. When you’re seeing this, are you in a box that has a fixed height, or an indeterminate height? I can’t recall which I saw.
Walter
On Jan 12, 2012, at 11:57 PM, David wrote:
I’m having an annoying problem. When typing text into an inflow item, the text I’m typing isn’t visible once I pass the end of the current text line. The curser moves down, and I can continue to type, but I can’t see the text. If I command-tab to a different program and back, the screen refreshes, and I can see what was previously hidden. When I reach the end of the that line and the next line starts, it’s the same thing. (There is a graphic footer image below the text, one that gets pushed down as the text area expands.) Is this a Freeway issue, a RAM issue…? Any thoughts?
This is happening while typing in a variable height CSS item. I just tried scrolling down and back up and that works, but it seems quicker for me to command-tab, command tab than to move to the mouse and scroll. At any rate, it’s good to know it’s not just me.