june07/NiM

Feature Request: Focus window only when debugger is paused

ceremcem opened this issue · 8 comments

ceremcem commented

The "Make Window Focused." option does not fit my workflow, so I disable it. However, it is useful to be notified when debugger pauses (at a breakpoint or when an exception is caught).

It would be helpful to have a "Make Window Focused On Debugger Pause" option.

june07 commented

A bit more testing on this code is needed but should have a working solutions soon.

june07 commented

@ceremcem Please give the newest release a try.

issue93

Also introduced a new image rotate utility.

nimRotateUtility

ceremcem commented

Hi,

I followed this blog post and updated NiM manually:

download the extension as a .zip by looking for the “Download ZIP” button on the right-hand side of the project page on GitHub. Now extract/unzip the code somewhere. Then in Chrome go to Menu (the three lines)->More tools->Extensions. Click the “Developer mode” checkbox and then click the button labeled “Load unpacked extension…”.

Now navigate in the resulting file dialog box until you are in the directory with a manifest.json file. For me, it was in the twlinkfy-master/ext directory. And that’s it!

However, it didn't work as intended with the following settings:

image

How it behaves

  1. When my NodeJS process restarted, it opens in a new, panel style window and gains focus immediately. (like the prev. version)
  2. When the debugger paused, it doesn't gain focus.

Extra odd behavior

Debugger attaches the process multiple times:

...(my application's console.log)...
Debugger attached.
Debugger attached.
Debugger attached.

System Information

Chromium Version 83.0.4103.116 (Developer Build) built on Debian 10.4, running on Debian bullseye/sid (64-bit)
june07 commented

Didn't consider the windowed mode! Just updated the code and added support for windowed mode.

https://github.com/june07/NiM/releases/tag/v2.7.1

Regarding the console messages, you will see one additional attach message due to NiM attaching in addition to DevTools.

Also you should be able to simply drag the zip file to your browser and install it that way. Let me know how that works.

ceremcem commented

Short feedback: Nope, it still behaves the same.

Also note that the behavior was the same on the previous version when I configured to "Open in tab" and not in new window. (So the problem shouldn't be related with that)

Also you should be able to simply drag the zip file to your browser and install it that way.

Didn't work for me. Maybe it's because Chromium and not Chrome.

june07 commented

FYI, confirmed different behavior on Linux today on my end. My primary development environment is on Windows.

  • 👍1