Unexpected WIDGET_TEXT behavior

[rdimeo]

I came across unusual and unexpected behavior when attempting to process events returned from a text widget. The following short program below demonstrates this behavior.

pro test_text_event,event
uname = widget_info(event.id,/uname)
case uname of
'QUIT': widget_control,event.top,/destroy
'N':    begin
            print,'TYPE: ',event.type
    end
else:
endcase
end
; ************************ ;
pro test_text
tlb = widget_base(/col)
void = widget_text(tlb,value = '10',uname = 'N', $
    xsize = 25, /editable,/all_events)
void = widget_button(tlb,value = 'QUIT', $
    uname = 'QUIT')
widget_control,tlb,/realize
xmanager,'test_text',tlb,event_handler = 'test_text_event',/no_block
end

The first time I run the program after doing a full reset (.FU), it does not return EVENT.TYPE 0 events after pressing ENTER (as I would expect a text widget should). Other event types seem to be returned properly. The next time I run the program (after NOT doing a full reset), when I change the text in the short program below and press ENTER, I get the following error:

NULL baseWidget (possibly Destroyed?) found in GDLWidget::PushEvent( WidgetIDT baseWidgetID=0, DStructGDL* ev=0x2e77cad56f0), please report!

So the WIDGET_TEXT does not seem to be returning events and event types as I would expect. And it also seems to depend whether or not I've done a full reset (though the behavior is still unexpected). Thanks in advance!

[GillesDuvert]

@rdimeo thanks for this nice bug report and how to reproduce --- will be cured soon

[GillesDuvert]

@rdimeo I've tested and do not have this behaviour at all. IDL and GDL behave the same. What I get is:

• cursor enter text area : nothing
• click to enter typing: event type 3
• type characters: event type 0
• delete characters: event type 2
• paste characters: event type 1

what is your platform ? ( !version and !gdl outputs)

[rdimeo]

GDL> print,!version
{

x64

Windows

Windows

Windows

8.2

Feb 21 2023
      64
      64
}

GDL> print,!gdl
{

1.0.2 Git

Feb 21 2023
  1676955600
   1
   0
   0
}

[rdimeo]

The unusual behavior that I described is repeatable in GDL (for me) but works as expected on IDL.

[GillesDuvert]

Ah, not fully tested under Windows, I'm afraid. wxWidgets may not behave exactly the same under Windows, eventhough they claim to be portable. Strangely, !GDL says it is compiled without wxWidgets ?

[GillesDuvert]

tested with windows 10, I find the same events as above, but text is not edited : that's already one bug.

[GillesDuvert]

Redone test. Apparently with GDL/wxwidgets one can get two '0' with one keystroke (adding a character), so indeed there could be a problem, although the handler is supposed to deal with any type of events and that's should be transparent. .FU seems OK, also. Opening an issue for this .