[BUG] s.meter only works after recompiling class library

[ckutzner]

Describe the bug
s.meter does nothing after starting sclang and booting the server, same with the keybinding I configured for this (F2). Only after recompiling the class library, the command or corresponding keybinding make the meter window appear.

s.freqscope, s.scope and s.plotTree are unaffected. The server boots normally, sound can be played without any problems.

Expected behavior
s.meter or the configured keybinding launch the server meter right at the first time.

Steps to reproduce

Additional context

Information

• Operating system
  Windows 10 Version 10.0.19044

• SuperCollider version
  3.13.0

• nvim --version
  0.9.1

• Package manager
  packer.nvim

• checkhealth output:

scnvim: require("scnvim.health").check()

scnvim ~
- OK nvim version 0.9.1
- OK sclang executable: C:/Program Files/SuperCollider/sclang.exe
- OK scnvim classes are installed: C:/Users/User/AppData/Local/SuperCollider/Extensions/scide_scnvim
- OK keymaps are defined

scnvim documentation ~
- using HelpBrowser for documentation

scnvim extensions ~

[davidgranstrom]

Hi @ckutzner,

Thanks for the report! I cannot reproduce the behaviour you are describing on macOS, but I have access to a Windows laptop so I will try this out shortly.

Do you experience the same issue if you run s.meter from the SuperCollider IDE?

[ckutzner]

In the IDE, everything works as expected!

[sadguitarius]

I'm experiencing somewhere similar on Windows, but in addition I do get the same bug with s.freqscope, s.scope and s.plotTree, as well as Help.gui, but not every time I start sclang, and sometimes one of these objects will not work when the others do. Things tend to work fine after a recompile. It's almost as if classes are getting compiled out of order somehow so they have missing functionality, although the language recognizes the object (its name appears in the post window) even when it does nothing.

I'm having a hard time figuring out whether this has something to do with readline/escape char stuff or if it's more of the side of GUI handling, but either way it's a weird bug for sure.