You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- We used show_popup two times, but it's a smoother experience to use
show_popup and then update_popup.
- There's a bug in ST where it thinks the view is modified when doing
a show_popup or an add_regions call with an edit token. Workaround
this by running sublime.set_timeout.
See: sublimehq/sublime_text#3424
- We used show_popup two times, but it's a smoother experience to use
show_popup and then update_popup.
- There's a bug in ST where it thinks the view is modified when doing
a show_popup or an add_regions call with an edit token. Workaround
this by running sublime.set_timeout.
See: sublimehq/sublime_text#3424
Description
When showing a popup with
view.show_popup
, one expects noon_selection_modified
callbacks to be invoked for that view.Steps to reproduce
cd ~/.config/sublime-text-3/Packages
mkdir Foo
cd Foo
echo 3.3 > .python-version
plugin.py
:Expected behavior
No prints to the console when hovering over a word in the buffer.
Actual behavior
The code above prints
yyyy-mm-dd HH:MM:SS on_selection_modified
to the console.Environment
The bug has also been verified on macOS 10.15.
Additional Information
If you change the python file as follows:
(So, the popup is shown right in the
on_hover
callback), then no on_selection_modified callback is invoked, as expected.Related on_selection_modified issues
#3398 (
view.add_regions
triggers it)#2990 (too many callback invocations for clones)
#1254 (mouse-up event should not trigger it)
The text was updated successfully, but these errors were encountered: