octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57635] Editor often has focus but no cursor u


From: Hg200
Subject: [Octave-bug-tracker] [bug #57635] Editor often has focus but no cursor until clicking elsewhere and then clicking in editor
Date: Thu, 23 Apr 2020 03:48:22 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0

Follow-up Comment #33, bug #57635 (project octave):

Ahhh - that makes a lot more sense! Thank you for pointing out this small but
important difference ;-)

I configured gdb to print a backtrace after a breakpoint is hit and let gdb
continue automatically. Because switching between the GUI and the gdb console
creates notify-events. It is like you said:

Scenario A:

1.) Two tabs are opened and one is closed with the mouse =>
m_edit_area->setFocus () is executed twice for the reasons
file_editor::active_tab_changed(int) and
file_editor::handle_tab_remove_request()
2.) Reimplementation octave_qscintilla::focusInEvent *is not* triggered. In
the GUI the focus is lost.


Scenario B:

1.) Two tabs are opened. Click the tabs with mouse to bring one into
foreground => m_edit_area->setFocus () is executed once because of
file_editor::active_tab_changed(int)
2.) Reimplementation octave_qscintilla::focusInEvent *is* triggered. In the
GUI the focus is correctly transfered.

This is odd ;-( The implementation of octave_qscintilla::focusInEvent looks
correct to me.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57635>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]