Why does the text cursor within interactor panes now appear hollow, as though you were not typing to the interactor?
Andy Hefner ahefner@gmail.com writes:
Why does the text cursor within interactor panes now appear hollow, as though you were not typing to the interactor?
My immediate suspicion lands on http://common-lisp.net/pipermail/mcclim-cvs/2005-October/000333.html, (but that's only a suspicion)
Cheers,
Christophe
Hi
On Tue, Dec 06, 2005 at 06:26:22PM +0000, Christophe Rhodes wrote:
Andy Hefner ahefner@gmail.com writes:
Why does the text cursor within interactor panes now appear hollow, as though you were not typing to the interactor?
My immediate suspicion lands on http://common-lisp.net/pipermail/mcclim-cvs/2005-October/000333.html, (but that's only a suspicion)
Yes, that's right. This behaviour was introduced by that patch by Rudi Schlatte; he has sent the patch to this list already on September the 24th. I have had a closer look at the patch after it was commited to investigate the problem, but, sadly, I've forgotten to write a report to the mailinglist. I only remember that the cursor-appearance is set to :SOLID at the wrong place so that it has no impact on the drawing. Hmm, ISTR a discussion about this on #lisp..
Sorry, Max
On 6. Dez 2005, at 04:33, Andy Hefner wrote:
Why does the text cursor within interactor panes now appear hollow, as though you were not typing to the interactor?
That would be because I suck :( I added behaviour to ports.lisp/(setf port-keyboard-input-focus) that toggles hollowness of cursors when the keyboard focus changes, which works nicely for text-fields and text-areas.
I didn't check the behaviour for stream panes before checking it in, and before real life intervened, I unsuccessfully tried to find the "real" cursor object for them. I suspect the cursor that is really drawn belongs to some Goatee instance inside the stream; witness the comment in frames.lisp/ default-frame-top-level: ;; We don't need to turn the cursor on here, as Goatee has its own ;; cursor which will appear. In fact, leaving it on causes much ;; bit flipping and slows command output somewhat. So, leave it ;; off by default, and hope this doesn't violate the spec. But I got lost inside a maze of objects.
Rudi
Ah, that makes sense. Goatee does indeed maintain its own cursor. Funny enough, I implemented this same thing (custom cursor shapes, focus sensitivity) locally about two years ago (and never committed..), and part of that was modifying Goatee to use the stream cursor as its own cursor (they're derived from the same classes anyway, so I only had to touch one or two places).
On 12/6/05, Rudi Schlatte rudi@constantly.at wrote:
I didn't check the behaviour for stream panes before checking it in, and before real life intervened, I unsuccessfully tried to find the "real" cursor object for them. I suspect the cursor that is really drawn belongs to some Goatee instance inside the stream; witness the comment in frames.lisp/ default-frame-top-level: