One of the users of a Windows 95 application I wrote and distribute within
Boeing just complained about the way the cursor works in an Oberon/F text
view. When using the space bar repeatedly to insert several spaces, the
cursor completely dissappears, so there is no way to tell when you should
stop spacing. I notice that in other Windows applications, the cursor always
stays visible, so this appears to be an Oberon/F-specific problem. Is there
a workaround for this? Also, is there a workaround to make the cursor a
little more bold and non-blinking, like most other Windows applications?
Thanks in advance,
Marc Martin
Boeing Commercial Space Company
Seattle, Washington, USA
marc.martin@boeing.com