T.R | Title | User | Personal Name | Date | Lines |
---|
1906.1 | known 'problem'... | SICVAX::GRAHAM | if ya want home cookin, stay home | Thu Dec 14 1989 01:39 | 8 |
|
I use,
*.*blinkRate: 0
on my PMAX.
Kris..
|
1906.2 | Blinking an INVISIBLE cursor?? | 34339::BRYSON | | Thu Dec 14 1989 10:26 | 8 |
|
I still like to see the flashing cursor in the active text widget. What I
thought was funny is that the Session Manager blinks an INVISIBLE cursor,
taking the 1% CPU to do something that is never seen. I knew that the
blinking of a cursor takes about 1% of the CPU. Is this then known feature
or is it the blinking of an INVISIBLE cursor that is a known problem?
David
|
1906.3 | | PSW::WINALSKI | Careful with that VAX, Eugene | Fri Dec 15 1989 18:34 | 6 |
| The text widget doesn't know enough not to blink when its window isn't mapped.
I find this an annoying enough problem that I've turned off blinking cursors
universally. Whether this is considered a bug is a matter of opinion. If you
think it is a bug, QAR it.
--PSW
|
1906.4 | The window is mapped... | 34339::BRYSON | | Mon Dec 18 1989 13:49 | 12 |
| It's not that the text widget is not mapped. It is. The situation is
that the cursor is INVISIBLE, that is has DwtNinsertionPointVisible set
to false. Eventhough the cursor is not visible, the simple text widget
will still trying to blink a cursor. Right now, this should be a warning
to anyone using simple text widgets with DwtNinsertionPointVisible set to
false -- the simple text widget will still try to blink the cursor so
the application should explicitly set DwtNblinkRate to 0 for these text
widgets with INVISIBLE text cursors.
Like I said originally, this is a trivial point.
David
|
1906.5 | useful 'bug'? | SICVAX::GRAHAM | if ya want home cookin, stay home | Tue Dec 19 1989 02:03 | 4 |
|
For Motif, blinkRate is a feature - and it is documented.
Kris..
|
1906.6 | please report this in the ULTRIX QAR data base | SMURF::HOFFMAN | anywhere in the universe | Wed Dec 27 1989 19:15 | 7 |
|
I would appreciate it if you would report this problem to the
UWS_QAR data base on the system GORGE. We need all the performance
(and easy workarounds) that we can get in the next couple months.
John Hoffman
UWS V4.0 Project Leader
|