Re: X-windows text events [message #30159 is a reply to message #30030] |
Fri, 05 April 2002 01:33   |
Niel Malan
Messages: 7 Registered: April 2002
|
Junior Member |
|
|
On Thu, 4 Apr 2002 09:52:27 -0700, David Fanning <david@dfanning.com> wrote:
> Niel Malan (Niel.Malan@aber.ac.uk) writes:
>
>> The idea of my line-based text widget is that it should only select lines, return the selected line as GET_VALUE, and
replace
>> the selected line with SET_VALUE. I do that by capturing events from a text widget, examining the position of the
>> cursor/selection, and then setting the selection to the beginning and end of that line. WIDGET_CONTROL's GET_VALUE and
>> SET_VALUE then uses this selection.
>>
>> The compound widget works well, but there is some side-effect behaviour. When the widget is first started, behaviour is
>> normal. However, once the compound-widget event handler has handled some events, events are generated for text selection
>> attempts on all open X-windows. Sometimes this behavior disappears after working in MS windows, but returns once the event
>> handler has handled events: I can't yet replicate this at will.
>>
>> The nett effect is that it is impossible to select text from other X-windows while my widget is running. This includes the
>> IDLE and IDL online help.
>
> Did I say "user did something wrong" theory? I meant
> "IDL is nuts" theory. Sorry. :-(
To be honest, I've also noticed some wrong-line selection during development, but it went away after I cleaned up and added
the out-of bounds handling.
> P.S. Let's just say I found list widgets handy for
> selecting lines of text. :-)
Now he tells me! But I want the GET_VALUE thing. Badly.
I'll probably be better off making a compound widget wrapper for a list widget.
Niel
|
|
|