Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Holding down F11 spawns multiple downloads #3

Open
JamesCaska opened this issue Feb 18, 2022 · 3 comments
Open

Holding down F11 spawns multiple downloads #3

JamesCaska opened this issue Feb 18, 2022 · 3 comments
Labels
can't fix - no control we've no ability to control this. it's a VSCode limitation

Comments

@JamesCaska
Copy link

Checklist:

  • [X ] I updated to the latest spin2 version available
  • [X ] I have restarted VSCode and the problem still exists

Version of Spin2 Extension with the issue:
5.9.8
Last working version (if known):

Hardware, Operating System, VSCode version:
Win11, VSCode 1.64.2

If I hold F11 too long (fat finger) multiple download sessions get spawned. The work arround is to just press quickly but it caught me out a couple of times.

If there is an existing download/terminal session then don't launch the new task or add extra delay

Additional information: (please attach your source file (.spin2) exhibiting the problem you are describing.)

@JamesCaska JamesCaska added the bug Something isn't working label Feb 18, 2022
@ironsheep
Copy link
Owner

@JamesCaska Interesting! I never thought to try this.

The maybe not so good news is that I'm not sure I have any control over this. We provided data to VSCode and it runs everything. We have no code behind-the-scenes.

Maybe there's a directive we can specify which tells the system to only allow 1 process at a time. I'll look into this.

More news after I've had time to look!

@ironsheep ironsheep added can't fix - no control we've no ability to control this. it's a VSCode limitation and removed bug Something isn't working labels Apr 16, 2022
@ironsheep
Copy link
Owner

I've not seen any means to address this within VSCode.

@JamesCaska
Copy link
Author

Ok.. well it's not a big deal. It's only happened a couple of times. I guess I automatically learn to avoid it after a while.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
can't fix - no control we've no ability to control this. it's a VSCode limitation
Projects
None yet
Development

No branches or pull requests

2 participants