[VCM] VCM utility moving to legacy in 0.67 timeframe (updated from community feedback)

Update from crutkas:
Based on community feedback, we'll be shifting the decision from removing the feature to moving it into a legacy mode (maintenance only).  This will still be in the 0.67 timeframe. Our team will only directly address critical bugs, security and accessibility issues.
We'll accept community PRs for enhancements but to date for VCM, has been small in comparison to others which was one of the supporting factors in our decision.
We love the community and feedback. Thank you for helping guide our decision.

What about Win10 users? They don't have the shortcut. I don't think removing the utility will make users happy.

This issue is the place to gather feedback like this.

Wait, but isn't this feature just for apps that support this. It doesn't work for all apps.
Also there is no feature for camera.

Yeah I'm confused too. I think the choice is quite definitive, so what kind of feedback do you want???
Discussions would be the place for either an Announcement or a Poll.

This issue is the place to gather feedback like this.

I use Windows 11 and use VCM a lot when using Zoom.  I love the new feature where the display stays on when on mute AND off-MUTE.  Please do not deprecate as it is a valuable feature.  For Win11, you should look at how you could tap into the mute button displayed in the taskbar to mute/unmute.  Currently this only works with MS-Teams but I believe it would VCM could be tweaked to enhance this capablity in Win 11

EDIT: @yuyoyuppe is this actually gathering feedback, or is this a firm decision? The fact that all the related issues have been closed and linked to this issue makes me thing this is a firm decision and not a feedback-gathering issue.

Same feeling. I strongly hope to retain this feature. I am also a win11 user.

This issue is the place to gather feedback like this.

I use Windows 11 and use VCM a lot when using Zoom. I love the new feature where the display stays on when on mute AND off-MUTE. Please do not deprecate as it is a valuable feature. For Win11, you should look at how you could tap into the mute button displayed in the taskbar to mute/unmute. Currently this only works with MS-Teams but I believe it would VCM could be tweaked to enhance this capablity in Win 11

Also I just tested the global shortcut (win+alt+k) in windows 11 and it doe not work with zoom.  You get a little pop-up that says "no supported apps in use for mic mute" for 2 secs and it disappears ...more reason NOT to deprecate VCM :)

What about Win10 users? They don't have the shortcut. I don't think removing the utility will make users happy.

Yes. totally agree. We would like to move to Win 11 but corporate world does not move that fast

If nothing else, it could be released as a standalone app so that people don't have to keep old PT versions around if they need it.

You also don't remove Fancy Zones just because Windows 11 has now better window management. Conference Tool is a must have features for PowerToys.

Lol, just now I wanted to start using VCM on my Windows 10 machine (I'm still on W10 for some more time), just because of the new 'hide when muted' feature. I really would like to use this feature on W10. What's the pain of keeping this feature for just W10 users? It probably requires a check though (code-related, to check whether the user is running W10 or W11, if that piece of code doesn't already exist).

Removing VCM completely because Windows 11 has a similar but worse feature doesn't make any sense, unless devs are planning on dropping support for Windows 10 outright.  Might as well remove FancyZones, Image Resizer, Shortcut Guide and probably others since there's similar but worse ways to do some of that in Windows already.

@crutkas @yuyoyuppe If VCM will be removed after v0.67 then it's too soon to actually close all VCM issues already. We can lock issues in the mean time

Look, I'm just going to parrot the same things as everyone else (and add one more):

Windows 10 exists
VCM is superior to what Windows 11 has anyway, thanks to it working all of the time instead of contextually
VCM is actually missing features, like Push-To-Talk and beeps when changing state

I think it is absolutely a mistake to remove VCM from PowerToys, especially as it is one of the major reason to install it in the first place.

Please continue to support VCM for at least Windows 10.  This OS is still heavily used, as many PCs cannot be upgraded due to hardware requirements.  This OS is also officially supported by Microsoft until Oct 14, 2025, so dropping support of VCM before then seems premature.

@yuyoyuppe
Please don't remove this very useful feature, it's about the only feature I use in PowerToys.
As others already have pointed out the feature you refer to in Windows 11 is not the same, and it only supports Microsoft Teams. As much as Microsoft would like it, not everybody exclusively uses its video conferencing software. Removing this feature will certainly not "force me" over to MS-Teams, but it will take away my incentive to use PowerToys at all.

Strange justification for deprecation; Windows 11's tool is flaky at best and only works with audio. As others have said, FancyZones is a superset of Windows 11's new tiling window manager. Why can't Video Conference Mute remain in PowerToys, given it's a superset of the new, inconsistent audio mute button in Windows 11?

VCM has more uses than just muting in common video calling applications, it's the closest thing to a hardware mute.
Why remove something because it's "not needed" when the entire program is OPTIONAL software...
VCM isn't redundant with the windows 11 feature and is irreplaceable on windows 10

Another vote to keep this feature!

Also hope this isn't removed. I'm on Windows 10, and without a new PC I cannot move to Windows 11 (missing secure boot, TPM ect) and I use the VCM almost daily during my work calls, except for weekends - Even then actually when working on-call. Please don't remove it

Why remove something because it's "not needed" when the entire program is OPTIONAL software

Well ... there's one reason I know of ... VCM hasn't has any significant improvement for a long time, even though there are a number of things that should be improved. I'm gonna omit the argument about installation (file) size.

Why remove something because it's "not needed" when the entire program is OPTIONAL software

Well ... there's one reason I know of ... VCM hasn't has any significant improvement for a long time, even though there are a number of things that should be improved. I'm gonna omit the argument about installation (file) size.

My uneducated guess with that is it since it took so long to get out of being experimental, it'll be a pain to maintain

The decision to remove the VCM feature from PowerToys is in my opinion, not a great choice. The built-in feature in Win11 isn't on par with the one you currently have in PowerToys. only muting the microphone in "supported" apps rather than system-wide is a MAJOR and I quote MAJOR downgrade. If the VCM feature from PowerToys should be removed, then the built-in version of it in Win11 should act just like it, not as a downgrade.

I'm not using Windows 11, so  there's no alternative in Windows 10. Windows 11 build-in mic mute is not 100% replacement for VCM either. And, to be frank, VCM is the only thing I'm using PowerToys for, and the only I got started using PowerToys in the first place. I have it bound to a mouse button, I can mute my microphones once an for all without worrying if app has a global mute or not. I have it bound to a button on my wheel, to mute/unmute microphone during gaming, etc. etc.  Ditching VCM is a dumbest decision ever, sorry.. hands down!

Lol VCM is like 80% of what I use from PowerToys. Why would you remove it

I agree with what people are saying, VCM is insanely useful to me running on W10. I probably won't be updating to any later versions of PowerToys if this feature is deprecated.

Just no!

您也不会仅仅因为 Windows 11 现在具有更好的窗口管理而删除花式区域。会议工具是PowerToys的必备功能。唯一支持Win + Alt + K的应用程序是Microsoft Teams。

是的，截止到目前

I wish I had something else to say, that hasn't been said already, but you said that you were accepting feedback on this matter. That makes it sound like there is a chance, given enough feedback, that you might reverse this decision. I use this feature literally daily with PowerToys, and would really appreciate if we could keep it. Even if you took it out of PowerToys and added it to its own standalone Install, that would be preferable vs Axing it entirely. I run PowerToys in both My Win11 and My Win10 Machines, and the Global Mute in Win 11 only seems to work with Teams, so its not really global at all. This feature is much more reliable, and just works. It definitely could use some enhancements, but even if it never got updated again, I much rather have it in its current iteration, then lose it entirely. I love the new additions to PowerToys, and really don't want to have to stop updating just so I can keep this vital function. Please Reverse course or compromise with you user base on this.
I am wondering if there is anyone who believes the Windows 11 "Global" Mute is an effective replacement? Also wondering if PowerToys is going to mainly focused at Windows 11 Users from this point forward?
Anyways, Appreciate the chance for discussion, I hope there is a chance that the community will be listened to on this one. Thank you!

Adding tot he feedback that this needs to stay, even if only on Windows 10 but ideally as it is, the Windows 1 feature is not global, won't work on Zoom and the camera feature is missing anyway.
Please don't deprecate this.

I never used this feature, but I am against removing something if there has not been a suitable replacement for all users. Decide not to keep updating it, maybe, but don't remove it totally. There is no reason for that. As a side note, it is nice to see Windows adding some features that originated in power toys. My wish is just that they would add it in its entirety, not seemingly half-baked...

Voicing my opposition to deprecating this feature.  I use VCM and I am currently on Windows 10 for the foreseeable future both at home and at the office.  As others have stated, the Windows 11 mute is not a suitable replacement in its current state either.

I also very much rely on VCM for my day to day work.  The option build into windows 11 doesn't support anything I use.
Depreciating this is a mistake.

Perhaps one option would be to fork off the VCM feature and leave further development to volunteers in the community?

I saw a stat the other day that Windows 11 has 20% adoption so far; seems counter productive to deprecate this feature for a minority of users?

It seems like 100% of the comments are against this decision
If the users are against it and it brings no benefit then the decision should probably be reversed

Both Google Chrome nor MS Edge does not support Win11 mute - thus it's not applicable for online meetings...

Does the development team want to force users to use the new features of Win11?

2597374584
@.***

------------------ 原始邮件 ------------------
发件人: @.>;
发送时间: 2022年11月3日(星期四) 下午4:30
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [microsoft/PowerToys] [VCM] Removing VCM utility warning (Issue #21473)
It seems like 100% of the comments are against this decision
If the users are against it and it brings no benefit then the decision should probably be reversed
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Why delete the VCM feature, when you can enhance it to work together with the Win11 global microphone mute shortcut (Win + Alt + K).
I mean VCM works perfectly together with my laptop's microphone mute button. Why not enhance VCM to work on specific apps and/or on all apps (even apps that doesn't support the Win11 global mic mute) depending on the settings. Maybe make the fly-out a bit smaller while your ad it. Or make it a notification or something like PowerToys awake, where it is sitting in the taskbar, so it doesn't disturb your screen.

Another request that this feature is retained. Lots of users (particularly corp users) will be stuck on Win10 for some time yet, and the built in Win11 features is inferior compared to PowerToys VCM.

Mirroring other comments, removing a widely used feature because an OS less than 20% of us are using has a worse feature is utterly ridiculous.
I won't be switching to windows 11 until you let me turn recommendations off completely, bring back a decent right click menu on the task bar and stop restricting access to the default right click menu meaning a ton of stuff now needs extra clicks.
And don't get me started on combining the battery/networking/volume together!
When windows 11 has feature parity with 10 then you can start removing stuff, not before

Both Google Chrome nor MS Edge (sic!) does not support Win11 mute - thus it's not applicable for online meetings...

So for a supposed universal feature it seems woefully lacking!

Win + Alt + K is NOT a replacement for VCM:

It's not recognized by all apps (right now I'm using discord and it's not working):

It doesn't have the option to mute camera
In some MS Teams if you use it, other people can see that you're muted
You can't use it as webcam source

It's really nonsense to remove such a great tool, just leave it there and maybe don't update it, but why do you need to remove it?
Personally, I hate the Windows 11 window snapping (it's one of the first things I disabled), I've been using Fancy Zones for years and I really don't understand why Microsoft introduced such a worse (and limited) experience:

You can't customize the areas
You can't have multiple setups and shortcuts
You can't press shift to merge multiple areas together

I hope that it won't get removed too because "Windows 11 already has this feature", otherwise that would probably be my last PowerToys version.

Since I personally use this feature a lot in Windows 10, I think I might stay on v0.66 or whatever last version VCM still exsists on in the future.

I am also on Windows 10 for the foreseeable future as my machine will never support Win 11. Please do not remove this feature.

I personally have two devices I use regularly, and neither are on Windows 11 yet. I am not happy with certain feature changes in Windows 11 so have not made the push until I am satisfied my workflow won't be hindered fully, plus one of these devices is straight up not supported due to the components inside, and I cannot afford to upgrade it at the moment. I do not see a reason for this to be removed as a feature when I can make good use of this feature, as can seemingly many, many people. This is a widely disliked move and if this is asking for genuine feedback and not a pre-determined choice, then please do listen to us all requesting this be kept given Windows 10 has no similar feature and Windows 11's feature is an opt-in implementation, not global.

I am also against removig VCM. The new Windows 11 feature lacks the functionality of VCM.

Using the Video Mute a lot and also don't want to see VCM going away. W11 feature is not the same.

I feel sad that besides all opposition in the comments, this deprecation sign has been released in the most recent update (I updated just a few minutes ago and found out about this). What's the purpose of getting "feedback" if such feedback is going to be completely ignored? Does the voice of the community matter?

I agree with everything that's been said on VCM and I agree. I'd just like to point out that win11 "compatibility" is just marketing BS so if you like the OS litterally just install it through rufus, it will also pick up the licence no questions asked.

I just started using PowerToys recently, and VCM is the best thing that came with it. Please let us keep it!

I am also on Windows 10 for the foreseeable future as my machine will never support Win 11. Please do not remove this feature.

I hadn't even considered users who can't upgrade to Win11 due to incompatibility.

VCM is about 95% of my usage of powertoys. Yes, I use other features but they are situational. Since I am a home office employe I have to mute-unmute mic all the time.
win + alt + k doesnt work system-wide as VCM is, so it is definetly not a replacement.

Currently, Windows 11 is on less than 16% of windows machines.
Desktop Windows Version Market Share Worldwide
Why on earth would you remove this functionality in 3 releases time?

win + alt + k   doesn't work in Google Meet 🤣
I am not joking.

Nice. It's 8 days since this issue appeared and... it has so many comments that only 6 issues have more. All those issues are at least 2 years old. 2 years.  Question is - what will you do now?

let's actually give feedback to not remove it and see if they even care.

VCM hasn't had a significant improvement in a while. I think, in the end, one of the reasonable possibilities is that VCM will be "extracted" to a standalone project/app.  Maybe then - whoever shall be maintaining it - can focus more on the project and it would get even better.

@shinayser it works only in apps that specifically opt into supporting it. So far that's Teams and maybe Zoom I think.

VCM hasn't had a significant improvement in a while.

This is hardly the user community's fault. If the team want to remove the feature, we can't stop them, but they need to be up front with the justification. Is it because Win11 (poorly) replicates the feature? Because the module doesn't have a champion?
I suggest the team get together and get clear on the messaging.

Well, as far as I can see, you will force me not to update to the v0.67...

All devices are on Windows 10.... welp.

VCM hasn't had a significant improvement in a while.

That's actually an argument to KEEP this feature.  It doesn't really need to be constantly "improved" if it works (which apparently it does, as evident from all the comments here).  Ideally, this is where you want your software to be, in an unchanging maintenance mode that requires little work from the devs and no changes to user experience...

Hi all, I updated the body of this and the title.  Great feedback here.  I'll paste my update here so anyone that subscribes can read it.
TDLR: we'll keep it in but in a legacy mode.
Tweaked description from above:

Update from crutkas:
Based on community feedback, we'll be shifting the decision from removing the feature to moving it into a legacy mode (maintenance only). This will still be in the 0.67 timeframe. Our team will only directly address critical bugs, security and accessibility issues.
We'll accept community PRs for enhancements but to date for VCM, has been small in comparison to others which was one of the supporting factors in our decision.
We love the community and feedback. Thank you for helping guide our decision.

Thanks for your wise decision and hard work. Love you guys, love Microsoft.

@crutkas @team. Thank you for actually listening to the community feedback and reversing the decision to depreciate VMC, respect!

I installed Power Toys specifically for VDM feature! ( since then i discovered all the other useful features, but VDM is what i was searching for when i found Power Toys)
It would have been great to have the option to always hide the toolbar (mute indicator).  I have been updating the program as soon as every update came, hoping to get this functionality. I was completely surprised when I saw you guys were thinking of removing the feature altogether.
Please, before you freeze development of VDM, is there any way to get the option to turn off the toolbar?  :(

I am also against removing VCM. The new Windows 11 feature lacks the functionality of VCM.

Between 2 different Alienware systems that are only 2-3 years old, worth several thousand dollars combined, neither support installing Windows 11, just sayin...

Between 2 different Alienware systems that are only 2-3 years old, worth several thousand dollars combined, neither support installing Windows 11, just sayin...

That hurts! Can I ask how come? CPU or TPM? Did you know of that one registry key that (usually) allows to circumvent that?

Between 2 different Alienware systems that are only 2-3 years old, worth several thousand dollars combined, neither support installing Windows 11, just sayin...

bypass it. I am using Windows 11 on 13-year-old HP Compaq 6530s. It runs smoothly.

VCM was the only reason for me to install Power Toys.
In the mean time Power Toys has some other nice features, but VCM is still #1. I would dearly miss it!

win + alt + k  doesn't work in Google Meet, neither Slack (i am on win 11 22h2). I am not joking.
Does anyone knows where this shortcut actually works?

I think it only works for teams.

Win + Alt + K 's function, even if implemented in the respective app, is not congruent with VCM'S function, a reliably disabled audio and/or video input on OS level.
I'm, juggling with half a dozen voice and or video comm apps, muting on OS level is that one killer feature I've installed Powertoys for. Setting + remembering hotkeys for each is a nightmare, using the same  leads to conflicts. VCM protects both my privacy & my comm partners nerves.
I do agree though this feature belongs into every desktop OS. But, pretty please, as a system-wide input mute.

Please DO NOT remove VCM. VCM and FancyZones are the two killer features in PowerToys. With multiple conference calls every day using multiple apps, VCM is absolutely critical. I can't update to any versions of PowerToys that does not have VCM.

We are not removing per the updated title and description

We are not removing per the updated title and description

Yes, I understand it's deprecated not removed yet. I've also seen how deprecated features tend to get removed soon after they are deprecated. I really don't want that to happen with VCM, since I consider that a critical feature for PowerToys. If PowerToys did not have VCM or FancyZones, I would stop using PowerToys. None of the other features are compelling enough to continue using PowerToys without VCM and FancyZones.

@erosen03 we hear you. We looked at data and areas where we get contributions. Based on feedback here we are not removing it.

I just hope vcm gets its last needed improvements before  putting it on ice.

Im launching PowerToys for the first time. I saw this feature. I clicked on the link that says "More information". I expected that it tells me WHY this feature is no longer available. The first post doesn't say that. It seems like its coming off from another discussion or issue but there is also no reference.
@crutkas: Could you please edit the first post and add a small note why this feature is not available or add a link to it? Thank you.

@symbai, i did update the top description and title.  We are not removing it per the updated issue description.

Soo... Now the text in the message in settings is incorrect

So just a few things:

Glad you guys reverted from removing to maintaining VCM in legacy mode, hoping this continues working for Windows 10 as it has been.
A briefing about the difficulty faced due to new Windows 11 shortcut might elucidate people who understand things a bit more, as when Google's Android OS made an in built call recording & screening feature they had also blocked the way other third party apps used to do so, I expect similar shenanigans here.
I'm currently sticking to Windows 10, not because Windows Settings says so but because a lot of stuff I need & use are still mainly compatible with Windows 10.
I hope people saying they don't see the point of PowerToys without VCM (& 1 or more favourite features) understand this is a open source community project, people make and maintain it out of their own time mostly. I'm sure there were some Microsoft OSS Devs here who also do various important stuff within paid time, but they are going to be far fewer than public contributors.

Thanks, that's my 2 (or 4 I guess) cents on this

Want us all to use teams? I think this feature is extremly important to all Apps, now only teams can work. That is robber

Please don't remove it. One of the best features of Power Toys!

Did anyone ever get this to work with Zoom? It always caused some weird issue for me.

Just wanted to add my voice here that I'm glad this feature isn't being deprecated now.  It's one of the features I use most.  Like others have said, our corporate laptops probably won't see Windows 11 anytime soon so this is still very much a useful feature.  Thanks!

Literally the only thing I use PowerToys for, and it's better than what Windows 11 offers.

Please don't remove it, my second favorite PowerToys feature!!

Why deprecate it though? Why only reverse your decision partially?

I second this. I guess most people that commented on this just were relieved that this function would not be removed, hence no further comments on the "depreciated" status.
But it's a valid question to ask, why depreciate one of the (subjectively) best features of the Powertoys?

VCM was the only reason for me to install Power Toys. In the mean time Power Toys has some other nice features, but VCM is still #1. I would dearly miss it!

Same here - it's the feature I use most often

win + alt + k  doesn't work in Google Meet, neither Slack (i am on win 11 22h2). I am not joking.
Does anyone knows where this shortcut actually works?

I think it only works for teams.

I'm not sure it even works in Teams (at least it doesn't seem to on my W11 22H2 PC)

Chiming in to ask that this not be removed. I use it daily, literally hundreds of times a day as I am on calls all day long and need to quickly mute.

This is a very valuable Feature for the remote first world we have been ushered into Please don't deprecate this.

The decision to have an opt-in mute function in Windows 1 is simply dumb: There is only 1 microphone (and 1 camera), and the user wants to control that. There are not a lot of users using different apps simultaneously that shall have different access to the microphone - but even if a power user needs that, he may want to cancel ALL usage of the microphone when there is background noise or even a fart. So, to disable that one microphone (and camera!) is NEVER a per-app-decision, but a question of privacy and personal rights. Thus, VCM currently is and will be needed until Microsoft builds a similar mandatory control into Windows, where it belongs!

If VCM ever does get moved back to active development, please consider adding support for Windows Media Foundation... https://learn.microsoft.com/en-us/windows/win32/medfound/audio-video-capture-in-media-foundation.  FYI, Chrome uses this API to detect webcams and at this time, only detects my physical webcam device... not the virtual "PowerToys VideoConference Mute" one.  To make Chrome detect the virtual webcam, I had to go into its "flags" and disable this API for video capture which forces it to use DirectShow instead.  Afterwards, Chrome will then see the virtual cam.  chrome://flags/#enable-media-foundation-video-capture
Cheers!

I use this feature every day. Please dont deprecate it. Lot of users on win 10 and win 11 will be left in dark

I really don't want to lose VCM,because I think it's a very important function.

I don't think it is the best option to remove VCM.

Win + Alt + K does not work when using a VDI (Citrix).

Something that seems crazy to me -- why have there been no new media keys defined in the USB HID for things like mic mute in the last 20 years?
Volume controls for output have been standard for years -- why not input?
Have tried a bunch of different approaches for doing volume mute and so far the Powertoys option is the only one that seems to work consistently -- most of the other options seem to have issues with working properly after resuming from sleep, depending on the order in which devices wake (i.e.: if an Elgato Stream Deck wakes before the mic, the mic toggle plugins tend not to recognize it properly).

Win + Alt + K does not work when using a VDI (Citrix).

As on a client accessing the VDI or on when PT is installed on the remote VDI?

Win + Alt + K is not from Powertoys, it's from Windows 11. And I meant that pressing Win + Alt + K in my Windows 11 client does not mute the microphone within the remote Citrix VDI.

Win + Alt + K is not from Powertoys, it's from Windows 11. And I meant that pressing Win + Alt + K in my Windows 11 client does not mute the microphone within the remote Citrix VDI.

Win + Alt + K only works in Microsoft teams.

If the app doesn't support Call Mute, VCM would still be important. I rely on VCM to always work and don't like the idea of a mute function that only works with a specific function, I just need a keyboard shortcut to mute the microphone.

My 2c, while I don't use VCM technically speaking, if the reasoning is likely at least in part due to some form of "the absolute latest version of Windows natively has even a slightly remotely equivalent feature" then to me that would also apply to to entirety of Mouse utilities as under the advanced mouse settings page (i.e on Windows 10, Settings Application -> Mouse -> Related Settings) has settings that are "technically" somewhat functionally equivalent.

"Find My Mouse" vs "Additional mouse settings" -> Pointer Options -> Show location of pointer when I press the CTRL key.
"Mouse Highlighter" vs "Additional mouse settings" -> Pointers -> pointer shadow / Display pointer trails.
"Mouse Pointer Crosshairs" vs "Additional mouse settings" -> Pointers -> "Precision Select"

Just noticed you're deprecating this. Disappointing because PowerToys is meant to offer more functionality than you get in Windows. Removing a feature because Windows has a lesser version of a feature smacks in the face the very reason we all use PowerToys.
I hope the team reconsiders this. Even if it is true that Win11 can mute teams globally, what about the the video mute?
*Note I'm still on windows 10, but by far the feature I depend on more is the camera mute, which wouldn't even work on windows 11 natively.

Quite disappointing how Windows 11 is being hard pushed even in PowerToys. Where the OS fails, OSS shines usually. And if this feature is stripped from PT, somebody else is porting the code over to another project. Nobody wins.

@Rekkonnect we are not removing it. Please read the opening statement.

WebEx now seems to support Win + Alt + K on Win 11. (Also a chance to chime in that the Shortcut Guide should show a lot more than what it currently does.)

First: I also would want VCM to stay, even though I currently don't use it because it is buggy AF.
I understand both sides. First, the Win 11 functionality is an atrocity, that is IF you even have Win 11. I won't. Ever. Maybe Win 13. And I also won't update Win 10 (to a newer subversion of Win 10).
But that's beside the point. Majority still uses Win 10 now, and even Win 11 users want the extended features of VCM that win 11 doesn't offer.
On the other side, VCM is a buggy mess. With sometimes the feed not coming back without reboot, and maybe the team (which is employed by Microsoft) might also be pressured to do so. (There comes no other reason into my mind why else Awake now has telemetry build in you can't see anywhere except the update notes nobody normally reads, and can't be turned off, other than the team was pressured to do so by a higher up)

I'd like VCM to stay because it's useful as a global mute function, whereas the Windows 11 feature requires support from individual apps. Even as a Windows 11 user, without VCM I won't be able to globally mute my mic anymore and will have to set mute buttons for every single program again. Please keep it in PowerToys. A global mute feature is far more useful than a mute feature that depends on app support in my opinion, regardless of how many programs the Windows 11 feature eventually supports.

In fact, the best way to control the camera and microphone is through video conferencing applications such as Zoom, but VCM is still very important, it should not be removed, because it has an "emergency operation" nature: in case of emergency, through the shortcut key trigger these functions. This is the same thing that happens with Fn+F4 (I use a ThinkPad)

Guys... VCM is not going to be removed.
However, I'd like to see some features added to it (like being able to mute NVIDIA Broadcast), and that's very unlikely.

VCM made me have a fun time with my friends during Zoom or GMeet. It should not be deprecated.

It's not going to be deprecated. :)

@felipecrs, according to what?

The very first post on this thread explains it.

@flyingwolf79,

(maintenance only). This will still be in the 0.67 timeframe.

Is that not deprecation by every sense of the term?

My understanding of deprecation is that it's something that it's going to be removed in a later version.

@felipecrs, whereas mine was that it merely implied lack or absence of maintenance. I understand your statement now. Apologies.

This is best feature on PT. So please DON'T!

Legacy mode is just one step away from deprecated. All it takes is one more update to change things in Windows itself to where this is completely broken. While I'm grateful it is not completely removed, this feature is an absolutely essential part of my daily workflow. I'm a Windows 11 user and the windows version is worthless. The global system mute that this provides is the right way to do things. This should not be "legacy", this should be a fully supported feature.

I can only repeat what other's said: I'm strongly against a removal or maintenance-only mode because even on Win11, there is no proper replacement

Agreed.
On Thu, Jan 19, 2023 at 9:33 AM itsTyrion @.***> wrote:

I can only repeat what other's said: I'm strongly against a removal or
maintenance-only mode because even on Win11, there is no proper replacement
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/21473#issuecomment-1397353776,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5LHLVXJJ3VKAA5JYX7VIL3WTF3IDANCNFSM6AAAAAARPHH6IU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I have no real problem with this becoming a Windows 11 only feature (although currently with Win 11 not being supported on a good chunk of PCs that people are still actively using the time to make additional features in Win 10 deprecated due to Win 11 replacements hasn't come yet IMO) but my problem is with how more limited that Win 11 implementation really is:
In Video Conference Mute I can directly choose which audio / video inputs to mute, with the Win 11 feature I can't.
This is especially a big limitation for those of us that require sound input devices for audio recording/editing or have external media devices (like the optical output of a TV) connected to them.

Hopefully the general feedback to this issue shows them, that VCM should still be actively maintained, at least until Win 10 & Win 11 have the same functionality built-in.

VCM is one of the PowerToys features I use the most, pretty much every day.
It provides a global toggle shortcut I can use for Discord and any other voice chat, and it's always the same keys, so I don't have to remember each combo for each individual game and app.
I wish that it was actively developed and improved upon, has a ton of potential.

@yuyoyuppe
Based on the feedback here, should PowerToys choose to remove this option from the global program would it be possible to spin it off as a standalone product?
That would be incredibly useful.

@flyingwolf79 there is nothing stopping someone from doing that. We are open source under an MIT license

Would love support for conference mute for Win 10 😢

@flyingwolf79 there is nothing stopping someone from doing that. We are open source under an MIT license

Well, how did I not catch that previously? Outstanding.

@crutkas @yuyoyuppe Since this is now in maintenance mode as opposed to deprecation, are you going to reopen the issues you closed as wontfix? I understand from the opening statement that your team may not address them all, but at least they'd be back in the queue.

I think the most useful thing about VCM is that it provides an easy way to overlay the camera video with an image (set the image when the camera is off and then turn off the camera). In this way, we don't need to install professional software such as OBS.

VCM is basically the only reason I use PowerToys. Please don't deprecate it. I have to use past version of PT if VCM is removed and I believe many users are same to me. It may not be actively maintained, but please don't remove this feature!

VCM is basically the only reason I use PowerToys. Please don't deprecate it. I have to use past version of PT if VCM is removed and I believe many users are same to me. It may not be actively maintained, but please don't remove this feature!

You can give MicSwitch a try. It's a small lil program that does the same. To be honest I want to switch to VCM though... but I wish we had the option to always hide the toolbar that pops up above everything :(

This is my most used feature in PowerToys... I think it's obvious from the reaction of the community that we love it and would not want to see it go!

I use it daily on work :(

It looks like they are still including the ability to turn it on, they just dont plan on continuing to update it. Makes sense if it's only useful in win10.

TL;DR: it's NOT only useful in win10.

I think it probably needs one more feature (but it's already maintenance only): auto-disable the microphone and camera at startup.
This would prevent malware from spying on the user. At least, VCM could help you detect that another program has modified the global microphone mute API, or actually it can't do that?
Or maybe the global microphone mute API doesn't help you stop some software from snooping through system-level drivers, and only manually disabling the microphone driver works? Can anyone tell me the technical truth?
Anyway, now I have to manually turn off the microphone and camera with shortcuts after every boot, which I think should be automated.

@rambda I agree that would be a nice feature, the good news is the code is open source and anyone could fork it and make that change.
I'm sad that it's in maintenance mode, but not sure we will convince them otherwise. I get a feeling that they are losing touch with what a "power toy" is (enhanced functionality above and beyond what is in windows and even in W11, this feature does more than what is built in)

@sirmeili we are prioritizing our time based on data and feedback. We are happy to accept any community contributions to improve the utility but we are focusing on other things right now.

Just wanted to add that in the current WFH situation, VCM has been one of the features of PowerToys that I have gotten the most mileage out of. Whether it's quickly muting myself because I have to cough, or mute and turn off the mic because I'm kissing my GF goodbye when she heads out, it's been an absolute lifesaver.
Thank you for not removing the feature alltogether, and I hope you will follow through on community PRs. I'm not much of a developer myself (anymore) but I'm confident in the community.

VCM is the sole reason I started using PowerToys. Everything else - there are plenty of toys/tools. I'd strongly suggest to not deprecate it.

VCM is the sole reason I started using PowerToys. Everything else - there are plenty of toys/tools. I'd strongly suggest to not deprecate it.

Check out https://github.com/iXab3r/MicSwitch

We'll accept community PRs for enhancements but to date for VCM, has been small in comparison to others which was one of the supporting factors in our decision.

Could it simply be that this portion of the program was simply well made and required little to no further feature updates? It sort of feels like you are not realizing that you are removing one of the features that worked so well that it did not need a bunch of community PRs.
Other than resizing or turning off the banner when the mic/camera is off being allowed, the VCM worked great. So there was not much that did need to be done, so you are getting rid of one of the easiest-to-maintain parts of your program.

@flyingwolf79 We're not removing it. We just stopped maintaining it.

@flyingwolf79 we will accept PRs but we will only handle a very small set of things as we are focusing on other things.

I do no understand the maintenance mode only, but in case it is about removing then no against it unless my vote really counts. If not removing but keeping it as is without further development or removing bug addressing(assuming no further time in development wants to be given to this) then also fine but removing it is not a proper fix or solution. It is useful and very much used. in fact was going to ask for a feature but now lets stick to keeping it for now at least.

VCM is one of the most useful features of PowerToys for me. It saves me a lot of time and hassle when I need to quickly mute my audio and video in Google Meet, and there is no replacement for it in this scenario (Windows 11 shortcut doesn't work with Google Meet). I'm sure this is the case for many other people who use apps other than Teams. You are basically abandoning a feature that many users rely on.
I think you should reconsider your decision and keep VCM as a fully supported and developed feature. Please listen to the feedback and don’t let this feature die.

Hello there: what are you attempting to do while the VCM were fell into legacy mode? Which stance can you define 'legacy mode' as?
If you had got the intention to kill the Vid. Conference Mute, are the feature is a deliberate integrate on Windows 10/11 starting with any new version from current [Win10 Final Version 24H2 and Win11 v23H2?] This benefit Google Meet and anyone who doesn't want a gank on COD:MWII open-mic proxichat and fail there, with a plus on all other apps on Win11/10.
Retiring the VCM permanently without nativing it entirely on MS Windows means that all users are forced to buy a hardware, or a download - this is not good.

I just installed Powertoys just because of VCM, only to find out it's in legacy mode (whatever that may mean...)

i really hope to don't remove VCM feature from powertoys, for me is a really must have also because i can't upgrade to W11 due to company policies and is really fast to disable & check mic really fast.
i would happy if you add more features to VCM, but nevermind, just don't remove VCM from powertoys, thanks a lot.

Could you please provide some context why this feature is put into maintenance mode? VCM is very useful for me, as I want to mute my microphone from time to time but do not want other attendees know.

Could you please provide some context why this feature is put into maintenance mode? VCM is very useful for me, as I want to mute my microphone from time to time but do not want other attendees know.

"Because it is available in Windows 11"
If you read the above consensus, it's an inferior implementation that is not a sufficient replacement for VCM.
I do not use VCM but I'm certainly not happy with a privacy tool being removed.

Please don't remove VCM; it is very useful.

VCM should be build-in windows function years ago. Please don't remove that feature from PowerToys

One of the most useful apps.... please don't remove it!

Do not remove it!
Having a global PushToTalk application bundled into the system is an incredibile feature!

One of the most useful apps.... please don't remove it!

Do not remove it! Having a global PushToTalk application bundled into the system is an incredibile feature!

It's not being removed, it's moving to legacy / de-prioritized. It still works; it's "complete".  I'm sure simple bug-fixes will be applied and it's just not being expanded.
If you want/need something that's "actively developed", there's MicSwitch which I just checked out today.

If you want/need something that's "actively developed", there's MicSwitch which I just checked out today.

it's unstable with a weird design.
This is not the tool i've looking for, also because (for me) i use VCM on my working laptop, so i need something really stable.
Anyway, since i use it daily and the development is only for bugfixes, i'll open an issue with the encountered bugs i've discovered.

One of the most useful apps.... please don't remove it!

Do not remove it! Having a global PushToTalk application bundled into the system is an incredibile feature!

It's not being removed, it's moving to legacy / de-prioritized. It still works; it's "complete". I'm sure simple bug-fixes will be applied and it's just not being expanded.
If you want/need something that's "actively developed", there's MicSwitch which I just checked out today.

Just tested it, did not work. only gui updates like mic icon but all the audio sources in OBS were still broadcasting the audio through to the stream. Also the UI is very unstable, many times does not open at all thus need complete kill from taskmanager and then a fresh start (if you have pressed hide in options) then forget that as well. In case someone using it wonders how to get it(UI) back, a workaround is to press mute shortcut, the icon in tray when is showing muted then double click but yes still unusable , a good attempt at solving the problem but as of now non functional and not even close to VCM.

It's concerning MicSwitch doesn't work for you two. Consider searching through the issues in that software, and opening one ticket at a time for individual issues you can reproduce. I think I might be able to reproduce the UI starting issue you both mentioned (software actively using a mic on launch?), and I'll open a ticket if/when I can figure it out.
I'm sorry you haven't found something working yet; I myself just discovered this feature in PowerToys the other day and would have also leaned heavily on using it.  :/
If it helps, these are my settings for using the ` key as a push-to-talk:

Click to expand

At any rate, I'm way off topic.

At the OS level is the best place for this sort of functionality to exist. I really can't fathom why the Win + Alt + K option is structured the way it is. Why force the burden onto app developers to integrate special muting functionality when the OS can toggle microphone volume and/or access for all apps? Similarly for the cameras. Win + Alt + K is useless to me as a Slack and DIscord user.
This is a disappointing move and the engineers and designers who implemented the Win + Alt + K functionality should consider community feedback and more common use cases because it seems they only did this in mind for Teams.

I will do you all one better: Win-alt-K doesn't even work in Teams Preview.
That's right, the future vision of Teams doesn't agree with this stunted, false future of VCM.

If VCM moves to a volunteer maintained stand-alone repository, it would likely no longer be signed. I would appreciate that if the decision is taken to separate it, Microsoft (or the PT team) would continue to lend their backing in that regard - keeping it accessible to many corporate users.
I appreciate the PT team being willing to leave this discussion open - it's not easy to see regular notifications of users disagreeing with you, but facilitating such conversations is an important aspect of mature governance❤

It's concerning MicSwitch doesn't work for you two. Consider searching through the issues in that software, and opening one ticket at a time for individual issues you can reproduce. I think I might be able to reproduce the UI starting issue you both mentioned (software actively using a mic on launch?), and I'll open a ticket if/when I can figure it out.
I'm sorry you haven't found something working yet; I myself just discovered this feature in PowerToys the other day and would have also leaned heavily on using it. :/
If it helps, these are my settings for using the ` key as a push-to-talk:
Click to expand
At any rate, I'm way off topic.

Tested this, it is buggy , ui sometimes loads and sometimes fails to load, above all the mic mute feature does not control mic as in my OBS the mic still takes voice input even if I mute it in this software. I think the software needs some more work to make it atleast functional and then more usable and then may be enhancing UI / UX . TLDR for now its not working.

To address the last few comments: We do not plan to move the codebase of VCM out of the PowerToys codebase. As previously said we just stopped maintaining it, athough we still accept Community PRs.

We will maintain the code base but no longer directly be adding new features. We will accept community PRs for the feature as well

@jeslinmx The fact that the new Teams does not support Win+Alt+K is super frustrating. There's feedback to Microsoft about it here, please go and upvote it! https://feedbackportal.microsoft.com/feedback/idea/2905367d-61df-ed11-a81c-000d3a0fab07

Good call to action. We need more people raising this issue so that the this will finally be fixed. Audio privacy is a right!

Thanks for nothing! Now I can't use PowerToys anymore on my Windows 10 computers :)
The best sentence of this post which makes me angry is "based on community feedback", LOL.

Now I can't use PowerToys anymore on my Windows 10 computers :)

FWIW the feature is still in the latest version (0.70.1) of PowerToys.

Thanks for nothing! Now I can't use PowerToys anymore on my Windows 10 computers :)
The best sentence of this post which makes me angry is "based on community feedback", LOL.

Care to actually elaborate? If you're having a real issue then report it.
Also.. You can just use an older version of the software

@Ruhrpottler  We test powertoys on windows 10. We kept it in due to people asking for it to stay. It is still there.

@Ruhrpottler We test powertoys on windows 10. We kept it in due to people asking for it to stay. It is still there.

And it would be foolish to stop supporting Win10.
It's clear at this point that Win10 is the King for "Modern Legacy" devices (Last BIOS, and old UEFI), whereas Win11 is for "Next Generation" devices that have proper hardware support for "future technologies" such as newer instruction sets or security... blah blah.
That being said it is appreciated, all the work that you and other members do.

@Ruhrpottler We test powertoys on windows 10. We kept it in due to people asking for it to stay. It is still there.

And it would be foolish to stop supporting Win10.
It's clear at this point that Win10 is the King for "Modern Legacy" devices (Last BIOS, and old UEFI), whereas Win11 is for "Next Generation" devices that have proper hardware support for "future technologies" such as newer instruction sets or security... blah blah. (not to diminish those technologies, most of us aren't there yet.)
That being said it is appreciated, all the work that you and other members do.

Also, there's a huge % of companies (like mine) that currently uses Win 10, saying "VCM will not supported because a similar feature is available on 11" in my honest opinion is unacceptable.

Oh no! ☹
I came to see this discussion after remembering about this part of PowerTools because of the Remote Desktop Connection bug (or Teams bug - I'm not sure which) that means my camera doesn't turn off at the end of a remote Teams call.
It's a faff to go into my host machine's Settings page each time to cycle camera options (although I could perhaps instead search for a way to pin a specific settings page to a shortcut, or see if I can createa a PowerShell script to cover my use case).

Can you please add the option to completly hide or  hide after 3sc  the toolbar : Microphone Off | Camera not in use

supplementary for toolbar: Can you add option to toolbar saying  Specific monotor let say monitor 2 or monitor 3 or likewise selecting individual monitor please. This is breakign many full screen games for example in my case valorant is broken and trackmania is also broken and Did not test but am sure it hinders any mouse and keyboard capturnign full screen game because of that toolbar present on main monitor only.

Sugestion: Adding selection of display monitor could solve this.
Thank you.

Can you please add the option to completly hide or hide after 3sc the toolbar : Microphone Off | Camera not in use

The only app that the Win 11 Universal Microphone app works with is the MS Teams 1 client.  Next month MS will be making the 2.0 Client the official client and as of yet, no support has been added for it.  So, it appears that even Microsoft is dropping support for the Universal Microphone button in Windows 11.  It doesn't even show up for me in my system tray when I join meeting anymore.

Can you please add the option to completly hide or hide after 3sc the toolbar : Microphone Off | Camera not in use

Could we have the option to specify how long it is displayed instead? I hate it when the volume button appears and then I have to wait before moving my cursor to that region or else it will stay for even longer. This is a feature that should be applied to all UWP applications.

Hey it would be awesome to add a button to swap the audio source, not the input but the output

It's still there in 0.73 and I hope it remains for the future! I disabled auto-updates, just in case. :)
Started using PowerToys for FancyZones, but enabled a few more features, including VCM, they're great so far!

It's still there in 0.73 and I hope it remains for the future! I disabled auto-updates, just in case. :) Started using PowerToys for FancyZones, but enabled a few more features, including VCM, they're great so far!

@benedekfarkas We do not plan to remove it. We just stopped maintaining it.

It's still there in 0.73 and I hope it remains for the future! I disabled auto-updates, just in case. :) Started using PowerToys for FancyZones, but enabled a few more features, including VCM, they're great so far!

@BenedekFarkas We do not plan to remove it. We just stopped maintaining it.

Love you Microsoft!

I recently updated PowerToys and VCM was disabled despite my settings, and the ability to turn it back on has been removed.  The option is completely grayed out.  I thought the feature wasn't being removed?

@kiddailey are you running as Admin? VCM can only be allowed in elevated mode.

@kiddailey are you running as Admin? VCM can only be allowed in elevated mode.

smacking forehead  Sorry about asking a dumb question.  Restarted as admin and was able to toggle it.  Restarted as non-admin and it was still enabled.  Thanks.

Not sure if said already, but a global microphone / video mute is essential to ensure that NO camera or mic can transmit sound or video no matter how the apps behave or "respect" the mute

Not sure if said already, but a global microphone / video mute is essential to ensure that NO camera or mic can transmit sound or video no matter how the apps behave or "respect" the mute

unfortunately they have stalled the development , it is now provided as is, so you can use it with whatever works for now. all the bugs and flaws remain with it since VMC is archived.

As far as I understood PRs are still welcome, even though it's in legacy mode.

As far as I understood PRs (for bug fixes or new features) are still welcome, even though it's in legacy mode.

i am not sure about that since last time i reported a bug where toolbar display is bugges ass to not be able to show it on selective monitor they said it is not worth fixing and closed it so yeha your experience might differ, for now i just regret why i do not know programming to fix thigns myself, there are so many projects on github that have lot of potential, okay i am digressing, in short with my experience they are not taking any bug fixes until it is in archive (as told to me while closing the issue) .
I do hope they bring this one back to fix remaining stuff. Nothing works as smooth as VMC when it comes to one click mute.

Can we please get the feature back? The global mute button of Win11 does not work with the new Teams client either so there is a high demand on global mute functionality.

The feature still exist . It is not removed. VMC is still there in Power toys adn you can use it.

Can we please get the feature back? The global mute button of Win11 does not work with the new Teams client either so there is a high demand on global mute functionality.

The feature still exist . It is not removed. VCM (Video Conference Mute) is still there in Power toys adn you can use it.

Can we please get the feature back? The global mute button of Win11 does not work with the new Teams client either so there is a high demand on global mute functionality.

My bad I saw the deprecation message and thought you can only turn it on if you where using it before (legacy mode). Starting the PowerToys with admin permissions solved my problem. But I am still wondering why you put it in legacy mode if you still collect feedback? Given the feedback here I think its pretty clear there is still a great demand of it, especially with Microsoft pushing the new Teams client now.

no idea, because "you" here is not me. but yes "they" might have their
reasons. I followed this for the argument over some bug fixes. Hope you
find yours justified. Rest of archival details are already discussed in
above comments or on other issues board. gud luck.
On Mon, 8 Jan 2024, 8:48 pm magic-happenz, @.***> wrote:

The feature still exist . It is not removed. VCM (Video Conference Mute)
is still there in Power toys adn you can use it.
Can we please get the feature back? The global mute button of Win11 does
not work with the new Teams client either so there is a high demand on
global mute functionality.
My bad I saw the deprecation message and thought you can only turn it on
if you where using it before (legacy mode). Starting the PowerToys with
admin permissions solved my problem. But I am still wondering why you put
it in legacy mode if you still collect feedback? Given the feedback here I
think its pretty clear there is still a great demand of it, especially with
Microsoft pushing the new Teams client now.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/21473#issuecomment-1881209951,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGLTF5KNB2RXKEH56IGNW6LYNQE23AVCNFSM6AAAAAARPHH6IWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBRGIYDSOJVGE
.
You are receiving this because you commented.Message ID:
@.***>

as a win 10 user i want this back

as a win 10 user i want this back

It is not gone, it just is not being updated with new features. Read the freaking thread dude.

Oh man, I also use it regularly, especially when in conferences. I really hope you reconsider this as it is for me one of the better features of powertoys.

You also don't remove Fancy Zones just because Windows 11 has now better window management. Conference Tool is a must have feature for PowerToys. The only app which supports Win + Alt + K is Microsoft Teams.

And unfortunately, even new MS teams does not support it

You also don't remove Fancy Zones just because Windows 11 has now better window management. Conference Tool is a must have feature for PowerToys. The only app which supports Win + Alt + K is Microsoft Teams.

And unfortunately, even new MS teams does not support it

@blowsie Support for the mute button for the new Teams comes mid-April.

Message id: MC709270
Roadmap link: https://www.microsoft.com/en-US/microsoft-365/roadmap?filters=&searchterms=191528

can we get this utility back, its really useful when you are on windows 10.

can we get this utility back, its really useful when you are on windows 10.

It is not removed, just not supported anymore

can we get this utility back, its really useful when you are on windows 10.

It is not removed, just not supported anymore

but it does not work , it says no camera found

I understand the reasoning behind this tool being deprecatred: it is focused on work (video conferences), it is useful to regular users, but requires local admin (which 99%+ of people, everyone outside IT, should not have on work devices), so it serves as a possible reason/excuse for reckless practices (end-users having admin).
Also, the reasoning for why it requires local admin makes sense - it affects input devices on a system-wide basis without other apps' voluntary cooperation, and isn't a built in system tool.  This can't be done without admin.
The solution is that Windows needs a built in direct equivalent, where the user sitting at the physical console can mute all audio/video input (in a way that isn't up to the apps to comply with or not).  Being built-in, it could be made to work without admin, just like the OS can allow an end-user to go into the settings and adjust Mic volumes to zero.  The constraints that require admin only apply because it's not an OS component.

In case the issue where the new Teams app doesn't work with the global mute button is the reason you were looking into this, it seems it's in development. Currently they're planning to start rolling it out in June.
https://www.microsoft.com/en-GB/microsoft-365/roadmap?filters=&searchterms=191528
Highly unpleasant that they're pressuring/forcing us to move to the new app already even though it's still lacking a basic feature, but it's more encouraging than nothing!

Hi, and thanks for the amazing work.
Another feedback is VCM is useful because Windows 10 and 11 don't have system wide push-to-talk shortcut as far as I know.
I am using it everyday for all sorts of apps.

Many of my work meetings have moved to new Microsoft Teams. I finally have a reason to use this feature, which works perfectly! I understand entirely focusing effort elsewhere but thank you for not removing it. New Microsoft Teams and the tray icon are in sync when using the mute mic and push-to-speak hotkeys.

This feature IS gone, isn't it?

I second those comments stating that just because a similar feature exists in the OS doesn't mean there's not scope to maintain a more flexible/complete version in PowerToys, or that anything that requires admin permission must be removed?  The thing is meant for power users, not just user level tools that have nothing similar available in the OS etc?  I don't trust the various software makers to respect my button presses to mute mic/blank webcam, they (for example) provide access to the people paying the service provider to remotely unmute it etc?  I've got a hardware control for my webcam so I can mute/blank that reliably, but when I'm using a bluetooth headset/4 pole headphones, having a global mute/blank function is very handy and a great assurance that you can safely visit the toilet etc without someone remotely unmuting your mic remotely etc 🤣.

I think I will have to stop updating PowerToys if this feature is actually removed.  A nice compromise would be to release the feature as a standalone application that can be installed beside PowerToys.

@mainsm

I think I will have to stop updating PowerToys if this feature is actually removed.

The feature isn't being removed.
The only way it might be removed in the future is if it becomes incompatible with the latest updates of the various supported Windows', and nobody submits bug fixes.
There wouldn't be any concept of using an old copy to keep the feature, because the feature wouldn't work.

As FYI for anyone looking for an alternative (admittedly a paid one), MuteDeck just got a lot closer to being a direct replacement for VCM.
They just released a new version this week that added the ability to set keyboard shortcuts for global audio / video mute:
https://mutedeck.com/blog/2024-10-14-mutedeck-v28-hotkeys-settings-loupedeck/
Still a few missing pieces (like hotkeys for "Push to Talk" or a combined "Mute Mic + Camera") that I posted requests for on their feedback tracker.
I'd started out using it in conjunction with VCM last year and for the past few months have been using it alone with VCM turned off.
Note that like VCM, it does still have the limitation that it can't listen to hotkeys that are pressed from within a Hyper-V VM.  For that I have an AutoHotkey script that runs with admin privileges to catch commands.  It was actually a little simpler to set that up with MuteDeck, since it has an API interface I can call directly with curl when I get a keypress event rather than needing jump through hoops to reissue keypress events on the host system.

Note that like VCM, it does still have the limitation that it can't listen to hotkeys that are pressed from within a Hyper-V VM. For that I have an AutoHotkey script that runs with admin privileges to catch commands. It was actually a little simpler to set that up with MuteDeck, since it has an API interface I can call directly with curl when I get a keypress event rather than needing jump through hoops to reissue keypress events on the host system.

This is going a bit off topic from VCM, but would you be willing to share your AHK script that listens for your keypress and sends it back outside of the VM?

This is going a bit off topic from VCM, but would you be willing to share your AHK script that listens for your keypress and sends it back outside of the VM?

I'm using a slightly modified version of this RDPHotkeyHelper script that passes media keys to the host:
https://github.com/neon-dev/RDPHotkeyHelper
That had a lot of stuff figured out already (like detecting when a VM is launched and rebinding keys so they still get captured), but all of the code for passing through keystrokes is based on single key events.
I ran into issues trying to come up with code to get key combinations to pass through and shelved the idea of using it for muting until I came across the MuteDeck API.
Here's the code that I'm using for calling MuteDeck (added right before the function definition for PassToLocalMachine):
; Control + Alt + Shift + A
^+!a::ToggleMute()
ToggleMute() {
	Run 'curl --silent -X POST http://localhost:3491/v1/mute', , "Hide"
}

If you wanted to adjust that to the same binding that VCM uses, you could use:
; Windows + Shift + A
#+A::ToggleMute()

As-is, it works OK with general RDP sessions to just drop it in a startup folder.
Hyper-V needs elevated privileges for intercepting key bindings, so I launch it via a Task Scheduler task with the following options:
General

Run only when the user is logged on
Run with highest privileges

Triggers

At log on

Settings

If task is already running, "Run a new instance in parallel"  (the script is set up to run as a singleton so it doesn't matter if it gets relaunched)

Closing in favor of https://github.com/microsoft/PowerToys/issues/36339

NO. Please do not close this in favor of REMOVING VIDEO CONFERENCE MUTE.

Please do not remove this. I use the Video mute portion of VCM every day! I get not wanting to maintain it, but why are you now removing it when this thread shows that there is a loyal user base for this functionality.
And before you say I can install it separately, I can't. Work has approved for me to install powerToys, but I can't just build the VCM on it's own and run it.

I've already said it as others have.  Disappointing.  I rely on this so much.  It's the most reliable, consistent, elegant, reliable way I have found to mute across a multitude of apps.

And before you say I can install it separately, I can't. Work has approved for me to install powerToys, but I can't just build the VCM on it's own and run it.

Well said.  It's really annoying when people assume you can just install any old software at will.

@mainsm

I think I will have to stop updating PowerToys if this feature is actually removed.

The feature isn't being removed.
The only way it might be removed in the future is if it becomes incompatible with the latest updates of the various supported Windows', and nobody submits bug fixes.
There wouldn't be any concept of using an old copy to keep the feature, because the feature wouldn't work.

You obviously have too much faith in Microsoft.....


One-step workflow for LAE Folders

Folders should only have one step: Make Public, or something similar. ("Complete"?). However, all this does is make the metadata record public. The images should be hidden until a second QA process happens. How do we want to do that?

I think this sounds like a three-state workflow:

pending
new state (discoverable?): public metadata but restricted images
complete

I wonder if "Pending" is useful?

We talked around that quite a bit, and I think everybody was fine with skipping the Pending state, and just starting with Discoverable.


Fix build warnings in Windows.

warning: passing argument 4 of 'event_set' from incompatible pointer type [-Wincompatible-pointer-types]
--> libevent expects callbacks to use evutil_socket_t for fd instead of int. Current code works fine in *nix because it's just int but not in Windows because it's defined as intptr_t.
warning: passing argument 4 of 'getsockopt' from incompatible pointer type [-Wincompatible-pointer-types]
--> Apply casting for Windows' getsockopt call
warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
--> Replace %lx with more portable %p. long is just 32-bit in 64-bit Windows.

fix_windows_warnings_test.log is the test log of this change.

No complaints, I think.

released in 1.6.4
had to adjust a bit for a clang warning in the %p bits


Skip the 'build_html' job on repository forks

The 'build_html' job fails on repository forks that do not have the gh_pages branch. This PR modifies the job so it is only run on the original Materials-Consortia/OPTIMADE repo.

Unfortunately, it seems that any non-zero status terminates the job so the job still fails on forks without this branch. I think
rewriting to something like:
git ls-remote --exit-code --heads origin refs/heads/gh-pages > /dev/null && exit 0

should work, but I should probably test it first before submitting another PR.

Ok, this approach does not seem to work in general. Exiting from the "Commit to gh-pages" job with a zero status results in the "Push changes" job still getting executed (and thus creating a "gh-pages" branch on the fork, but without the HTML pages). I will leave this alone unless the separate repo approach does not work out.

Ah, the following steps would have to be updated as well to do nothing. So, should we revert this merge?

We probably should since it is a bit misleading (comments do not match the actual behaviour). Is there an easy built-in way to do so in GitHub?

The merge icon in this PR thread had a "Revert" button. I clicked that, and it created a revert PR.


List Vault Items within recipe

Is there a way to perform the rough equivalent of knife vault show VAULT within a recipe? I would like to build a list of all items, then iterate over that list to do what I need to do with the data in each item. If not, I would like to submit this as a feature request.

A vault is just a data bag, so you can use the method in https://docs.chef.io/dsl_recipe.html#data-bag to iterate, and then chef_vault_item rather than data_bag_item

Calling data_bag() on a vault returns the ids of both the items and their associated keys, which forces users to check whether the current item being iterated over is the key or the item itself. I think a helper method that only returned the items in a vault would be a much cleaner implementation.

If you'd like to submit a PR to do this we'd definitely take it.


update chevron icons + add classname to svg string export

solves #113 and #111

Are class names now added automatically with the new version of svg-to-js?

yes!

ny patch-version ute nå


Add ssl URL parameter to download to override profile setting

Allow a user to pass a ssl flag to download.php which will override that user's profile setting on which announce url to use.

Done in 9d8357816097a3bb9e81ae8ae9d7b1bd23ded7a5


Does Dream.run clobber terminal line wrapping setting, and depend on TERM=xterm-256color?

Dream.run, if not called with adjust_terminal:false, sets some terminal settings, and then tries to restore them on exit (code below).

[ ] We have switched to Ctrl+C for exit. Are the settings being restored during exit by Ctrl+C? This can be checked by inserting a print_endline into the restore_terminal function, and just making sure the print occurs.
[ ] @thangngoc89 reported Dream messing with the terminal somehow inside tmux, where TERM wasn't originally xterm-256color. Is the way Dream is changing the settings portable across terminal emulation modes?

In the future, either the log will be terminal width-aware, or we will probably just use dumb line wrapping, and always behave as if adjust_terminal:false at the Dream.run level.
https://github.com/aantron/dream/blob/b8a46f4649d9ca296d89b49acd55aed8a7e29a41/src/http/http.ml#L818-L838

restore_terminal was not being called on Ctrl+C, but it does with this PR.

I think the first part of this issue was fixed in #151. I'm not observing any issues with tmux at the moment.


Cookies not working in GhostDriver JS?

My code is:
	StringBuilder script = new StringBuilder();
	script.append(" var c = document.cookie;");
	script.append(" var name = '__test_cookie__';");
	script.append(" document.cookie = name;");
	script.append(" return document.cookie.indexOf(name) !== -1;");
	Object res = driver.executeScript(script.toString());

and the result is false...
Do I have to configure something? This code (and probably other code for cookies) is used by webpage I want to test...

I found, that after
document.cookie = name;

it is still empty, at least for
return document.cookie;

Ok, investigating further and I found, that when I change
 var name = '__test_cookie__';

to
var name = 'a=__test_cookie__';

it works, now I'm not sure, in ChromeDriver it is not a problem...

PhantomJS issue created - https://github.com/ariya/phantomjs/issues/12885


Clarify namespace watching in the docs

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
This post https://kubevious.io/blog/post/comparing-top-ingress-controllers-for-kubernetes states the following:

Kong doesn’t support cross namespace, which means the ingress controller’s functionality is limited to a particular namespace.

while this issue https://github.com/Kong/kubernetes-ingress-controller/issues/683 made by an employee of Kong Inc. states:

Currently, it is possible to either configure the controller to listen for all resources from all namespaces (default) or one specific namespace.

A similar statement can be found in the docs right after the namespace paragraph:

If Kubernetes Ingress Controller is being used to proxy traffic for all namespaces in a Kubernetes cluster, which is generally the case, [...]

Who is telling the truth? I haven't been able to find the specific configuration in the docs or helm charts which would configure which namespaces are to be handled. Where do we specify whether KIC has to handle all namespaces or a selected one?
Proposed Solution
Add a corresponding information to the documentation. Contact the blog post author to fix their article.
Additional information
No response
Acceptance Criteria
No response

It looks like this is resolved. Let us know if you have further questions.


Unable to load DLL 'libuv': The specified module could not be found.

I just cloned this solution, created the SQL Server database, tried running it two different ways,

by clicking the IIS Express button in VS
at the command line, entering "dotnet run"

I get the same error.  I investigated on StackOverflow and there was some mention of adding a new element to the .csproj file, like so:
<PropertyGroup>
    <RuntimeIdentifier>win7-x86</RuntimeIdentifier>
    <BaseNuGetRuntimeIdentifier>win7-x86</BaseNuGetRuntimeIdentifier>
</PropertyGroup>

This is the original section:
<PropertyGroup>
  <TargetFramework>net461</TargetFramework>
  <PreserveCompilationContext>true</PreserveCompilationContext>
  <AssemblyName>ContosoUniversityCore</AssemblyName>
  <OutputType>Exe</OutputType>
  <PackageId>ContosoUniversityCore</PackageId>
  <PlatformTarget>AnyCPU</PlatformTarget>
</PropertyGroup>

... and this is the modified section...
<PropertyGroup>
  <TargetFramework>net461</TargetFramework>
  <PreserveCompilationContext>true</PreserveCompilationContext>
  <AssemblyName>ContosoUniversityCore</AssemblyName>
  <OutputType>Exe</OutputType>
  <PackageId>ContosoUniversityCore</PackageId>
  <PlatformTarget>AnyCPU</PlatformTarget>
  <RuntimeIdentifier>win7-x86</RuntimeIdentifier>
  <BaseNuGetRuntimeIdentifier>win7-x86</BaseNuGetRuntimeIdentifier>
</PropertyGroup>

It still produces an exception, but this time it's a BadImageFormatting exception.
Any ideas how to get this to run?

No idea!
On Tue, Jun 25, 2019 at 10:04 PM King Wilder<EMAIL_ADDRESS>wrote:

I just cloned this solution, created the SQL Server database, tried
running it two different ways,

by clicking the IIS Express button in VS
at the command line, entering "dotnet run"

I get the same error. I investigated on StackOverflow and there was some
mention of adding a new element to the .csproj file, like so:

win7-x86
win7-x86

This is the original section:

net461
true
ContosoUniversityCore
Exe
ContosoUniversityCore
AnyCPU

... and this is the modified section...

net461
true
ContosoUniversityCore
Exe
ContosoUniversityCore
AnyCPU
win7-x86
win7-x86

It still produces an exception, but this time it's a BadImageFormatting
exception.
Any ideas how to get this to run?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jbogard/ContosoUniversityCore/issues/34?email_source=notifications&email_token=AAAZQMX6RM55CA7CXPGHQU3P4LME7A5CNFSM4H3OATT2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G3WI6WQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAZQMXQXL7QUIUL6SKNESLP4LME7ANCNFSM4H3OATTQ
.


Lb maxconcurrent req

Addition of the Loadbalancer Max Concurrent Requests annotation to manage the following possible values (validated API side) 10000, 20000, 30000, 40000, 50000

lgtm


fix: do want aws_for_fluentbit module create cloudwatch log group

What does this PR do?
🛑 Please open an issue first to discuss any significant work and flesh out details/direction - we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

Motivation

Resolves #408

More

[X] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
[X] Yes, I ran pre-commit run -a with this PR

For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

After fix that.

The config will have good format.


Bug: Url on Address bar now correct with current page

Thank you very much for your contribution, but I am still unable to use this feature successfully
For example I have a local url for http://localhost:8002 . Whether I click to jump to the other local page or the external page the url in the address bar has not changed

After testing, it was found that the proxy mode must be used in order for the address bar to change according to the page changes

This is a very good extension that I use on a daily basis with high frequency.
Please continue to optimize it. Thank you very much


opensnoop: CO-RE tracer tries to open non existing tracepoint on ARM64

ARM64 doesn't have a open syscall. While testing https://github.com/kinvolk/inspektor-gadget/pull/441 I found that our implementation fails with
Gadget opensnoop: falling back to standard tracer. CO-RE tracer failed: error opening tracepoint: trace event syscalls/sys_enter_open: file does not exist

We should modify the tracer to not to trying opening this tracepoint when running on ARM64 as done by opensnoop in bcc-libbpftools https://github.com/iovisor/bcc/blob/c9635f8aa5e974bb30d5a7935054878a6eb5af53/libbpf-tools/opensnoop.c#L254-L262

I already met this problem.
I think the solution could be something like:
#if defined(__TARGET_ARCH_arm64)
// tracepoint for arm64
#else
// "default" tracepoint
#endif

I think this is not so complicated to handle (compared to incomplete BTF problem), so I first wanted to gather information on others problem before focusing on this one.


Bug 1819308: Deleting a CSV removes related CSV metrics

Problem: When creating a CSV fails, deleting it did
not clear the CSV metrics. So, when the same CSV was created
again and allowed to succeed, the olm pod still retained the
old CSV metrics
Solution: Added a new method that deletes the CSV metrics when the CSV gets deleted
Signed-off-by: Harish<EMAIL_ADDRESS>
Description of the change:
Motivation for the change:
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /docs
[ ] Commit messages sensible and descriptive

waiting on #1439 to merge to restructure the e2e test

/approve

/retest

/lgtm

Hey guys, in which release will this fix be available?

@jjaferson we're in the process of cutting a 0.15.1 release. This fix will be available as soon as the 0.15.1 is up in a couple of hours.

/cherry-pick release-4.3


Low code coverage

Low code coverage
Severity: Informational
Type: Code Coverage
Not all functions and execution paths are tested in the /tests directory. Consider adding more tests, and basic fuzzing tests for functions that are responsible for the core business logic.
In addition to add more tests that target different contract states, it is recommended to add minimal integration tests that chain together multiple different calls to the contract.
It is highly recommended to add more tests for all public functions in the vault/src/main.sw contract, particularly the swap() function.

acknowledged, thank you. This is a todo and still in the works


README example causes ember error

Trying to create a simple controller with a boolean flag attribute, and the code:
{{x-toggle value=flag onToggle=(mut flag)}}

As taken from the README, Ember raises an error:
Assertion Failed: You modified flag twice on <webapp@controller:session/index::ember903> in a single render. This was unreliable and slow in Ember 1.x and is no longer supported. See https://github.com/emberjs/ember.js/issues/13948 for more details.

Tested with latest ember-cli-toggle (v2.0.2) and Ember 2.10

Thanks for reporting.

I'm running into the same issue on emberjs 2.10.2. Happens during the initial load.
The stack trace of the failure is on the x-toggle component: line 47 -> 182

Also I noticed that the double rendering issue happens only when the initial value is false.

Not undefined?

correct

Might have been an error on my side as I copied the example which was (mut myValue) instead of (action (mut myValue))

Give v3.0.0 a try.


This wont run on my mac and I have FFMPeg installed

Fatal error: Uncaught exception 'Exception' with message 'FFmpeg is not installed on host server' in /Applications/XAMPP/xamppfiles/htdocs/ffmpeg-php-master/provider/FFmpegOutputProvider.php:50 Stack trace: #0 /Applications/XAMPP/xamppfiles/htdocs/ffmpeg-php-master/FFmpegMovie.php(220): FFmpegOutputProvider->getOutput() #1 /Applications/XAMPP/xamppfiles/htdocs/ffmpeg-php-master/FFmpegMovie.php(209): FFmpegMovie->setProvider(Object(FFmpegOutputProvider)) #2 /Applications/XAMPP/xamppfiles/htdocs/t.php(11): FFmpegMovie->__construct('/Applications/X...') #3 {main} thrown in /Applications/XAMPP/xamppfiles/htdocs/ffmpeg-php-master/provider/FFmpegOutputProvider.php on line 50

May be related to https://github.com/CodeScaleInc/ffmpeg-php/issues/27

I have to put the complete path to ffmpeg: /usr/local/bin/ffmpeg
If you have problem with DYLD_LIBRARY_PATH use this:
exec('unset DYLD_LIBRARY_PATH ;');
putenv('DYLD_LIBRARY_PATH');
putenv('DYLD_LIBRARY_PATH=/usr/bin');

SO answer

Closing this. @orlleite thanks for providing advice. @OElesin hoped it helped you.

I'm having the same issue. I did define the
public function __construct($ffmpegBinary = '/home/user/bin/ffmpeg', $persistent = false) {
The version Im using is ffmpeg version N-84660-gd92ad42 , does it not being a number have anything to do with the issue? just typing ffmpeg or the above directory/ffmpeg shows the ffmpeg information just fine via command line but no luck on this end. Thanks

@pokepud3

Yes just grabbed it from the tarball. 2.9.0

Then I guess it's a problem of parsing output of your version of ffmpeg. This library is currently tested on 3.2.2 ffmpeg version and on this version it works like a charm.
What is behind the cryptic N-84660-gd92ad42 ? I tried to search for commit hash of this version but no success https://github.com/FFmpeg/FFmpeg/commit/gd92ad42.

I installed it using this: https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu. Latest snapshot build.
wget http://ffmpeg.org/releases/ffmpeg-snapshot.tar.bz2 Latest snapshot from ffmpeg. Installed it yesterday. That's just how they are named.

Install 3.2.2 version and everything should work as expected. This is the latest version this library is tested against. If for any reason you need higher ffmpeg binary version, it is possible that this library works as well but from what you are reporting it seems like ffmpeg binary changed its output and our parser cannot compensate. It will take some time until we support latest ffmpeg version 3.2.4.

I'm fairly sure that's it. Will do. Thanks!

See the build log here: https://circleci.com/gh/char0n/ffmpeg-php/56?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
It show how we install ffmpeg binary to test it on ubuntu. The key is here:
sudo add-apt-repository ppa:mc3man/trusty-media -y

Tried it with ffmpeg 3.2.2 with the same error.  Does the files need to be in the same directory as ffmpeg?
ffmpeg version 3.2.2 Copyright (c) 2000-2016 the FFmpeg developers
built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4) 20160609
Fatal error: Uncaught Exception: FFmpeg is not installed on host server in /home/ftp/files/ffmpeg-php/provider/FFmpegOutputProvider.php:50

Hi again, then I guess it has something to do with how macOS passes output from its processes to php script. There something non standard there.
ffmpeg-php is almost 8 years old project so it can be tested on older PHPUnit versions only. Use e.g. PHPUnit 3.7.18 to make it run. We are already working on PSR-4 compliant version of ffmpeg-php here https://github.com/char0n/ffmpeg-php/tree/PSR-4-develop. Just be patient ;]
I guess in your case, it is about finding out why $output is empty: https://github.com/char0n/ffmpeg-php/blob/PSR-4-develop/src/OutputProviders/FFMpegProvider.php#L53
I will be something platform specific. I cannot do it for you, I don't have a macOS system. Can you do it ? I can guide you through.

I just noticed that this thread is for mac. I'm not using a mac. I'm using Ubuntu 16 LTS.  I can provide you my login info for the server, if you want to take a quick look.

Well why not. I guess I can squeeze 10 minutes tonight to have a look at it.
<EMAIL_ADDRESS>

Resolved. Permission issue.

@mayoalexander to tell you the truth I don't remember. It's been 4 years since this issue. Can you describe what problems are you seeing specifically?

@char0n im getting the same "ffmpeg is not installed on the host server." you mentioned it might be a permissions issue; i used another solution that ran ffmpeg via an exec() & system() function, so i know FFMPEG is installed. im assuming it must be something with the code trying to reach something it doesnt have permission to.
I also reached out to GoDaddy about the note you listed in the Readme about the partnership. Unfortunately they were not familiar with with the package :(
Feel free to email me if you'd like<EMAIL_ADDRESS>

@mayoalexander the library is running ffmepg via exec as well. It's assuming the name of the binary is ffmpeg.
We need to debug FFMpegProvider class and find out if the detection of ffmpeg works. What is the version of ffmpeg you're using?

In my case exec() was in php.ini's disable_functions list. Commenting disable_functions helped fix this.


Implement Regexp#match

Blocks GH-85.

Implemented Regexp#match? in GH-93.

Implemented in GH-103.


Refresh CUDA 12 migrator

Recently the CUDA 11.8 migrator was closed out ( https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/5340 ). As part of that it was determined a small updated was needed to the CUDA 12 migrator ( https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/5340#discussion_r1441268175 ). While this largely works for most feedstocks without changes, those that have use_local: true will have issues with re-rendering until the CUDA 12 migrator they have is updated. This PR pulls over those updates to fix re-rendering on the feedstock. Please let us know if you have any other questions.

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #25.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed.

Fixes #25

@conda-forge-admin , please re-render

This is passing! 🎉
@conda-forge/qiskit-aer this is ready for review 🙂

Thanks Bas! 🙏


Compiled bin files

I am having real trouble trying to compile the firmware for my T-watch V3.
Is anybody able to help me out and compile a bin file for me to flash please.
Thanks

I have managed to compile the firmware for V3 watch and have the bin files with esp flash tool config if anyone needs them.

I have managed to compile the firmware for V3 watch and have the bin files with esp flash tool config if anyone needs them.

Hey I could do with a copy!, if you'd be so kind.. i'm trying to get it to work with the T Watch S3..

I have managed to compile the firmware for V3 watch and have the bin files with esp flash tool config if anyone needs them.

could i get a copy perhaps?


Object.assign not working with inheritance

Is this a bug report?
Yes

Did you try recovering your dependencies?

Yes
Which terms did you search for in User Guide?

Environment

System:
OS: Windows 10
CPU: x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Binaries:
npm: 6.5.0 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 44.17763.1.0
Internet Explorer: 11.0.17763.1
npmPackages:
react: ^16.8.3 => 16.8.3
react-dom: ^16.8.3 => 16.8.3
react-scripts: 2.1.5 => 2.1.5
npmGlobalPackages:
create-react-app: Not Found
Steps to Reproduce

create-react-app test --typescript
add the following code to App.tsx

class A {
  constructor(...parts: Partial<A>[]) {
    Object.assign(this, ...parts);
  }
}

class B extends A {
  id: string;
  constructor(...parts: Partial<B>[]) {
    super(...parts);

  }
}

const a = new B({ id: '123' });
console.log(a);

run and look into console

Expected Behavior

The output in the console should be: B {id: '123'}
Actual Behavior

Actual output is: B {id: undefined}
Reproducible Demo

Found the solution here:
Babel issue


[Marketplace]: long name and description without spaces of custom app displayed overlapping application view form

EPAM AI DIAL chat version
0.18.0
How to reproduce
Steps:

create custom application with name of 150 symbols without spaces
add description with 150 symbols without spaces
save app
click on app card in My application -> application view form is displayed
click Use application and view start screen

Actual result

Name is overlapping the form
Description displayed in one line with horizontal scroll

Expected result

Long names and descriptions should be truncated with 3 dots
name should be truncated, description should be displayed in several lines

Confidential information

[X] I confirm that do not share any confidential information

fixed in #2086 with truncating with 3 dots custom application's name


An Example for UIVerticalScrollBar

Is your feature request related to a problem? Please describe.
I've followed the docs and now have a scroll bar showing in the window but whilst it moves up and down in response to the mouse it doesnt change the internal areas visibility/position.
Describe the solution you'd like
An example in the examples repo that shows how to use the vertical scroll bar to display information held in a container that exceeds the size of the outer container.  e.g. some UITextBox's inside a UIWindow.
Describe alternatives you've considered
Copying the code from the UITextBox into the UIWindow class. Having the UIWindow automatically add the scrollbar, like the UITextBox, when the contained content exceeds its size, would be ideal.
Additional context
https://i.imgur.com/NnlrHpj.png

There are two slightly different examples for this sort of thing at the minute:

Is just the message box window which shows how to stick a single text box inside of a UI window. This one is just for text.
Is the UICanvasWindow  in the Pygame Paint project which uses the UIScrollingContainer . With it you can have any UI element in a vertical and/or horizontal scrolling area. This project doesn't work particularly well in pygame 2 at the minute, but that's not because of the scrolling area.

Basically as you've discovered the scroll bar on it's own is not enough, you need to connect it to an area to scroll which can get quite complicated which is why I have built it in automatically to the text box and to the scrolling container. I would guess that you should be able to stick multiple scrolling or non-scrolling text boxes inside of a scrolling container, though I haven't built out UIs that are that complicated yet myself.
For various reasons automatically changing the size of the scrolling area based on the contents isn't always desirable but I suspect there will eventually be a variant of the scrolling container, or an option, that enables a more limited scrolling container that does expand to the right and left if things are placed outside of it's boundaries. Though changing the scrollable area yourself is not that hard. see:
self.scrolling_container.set_scrollable_area_dimensions((new_width, new_height))

Ah, I didn't see scrolling container. That might be all that's needed. I
might have missed it in the examples folder and docs - sorry about that!
On Mon, 13 Jul 2020, 14:09 Dan Lawrence<EMAIL_ADDRESS>wrote:

There are two slightly different examples for this sort of thing at the
minute:

Is just the message box window which shows how to stick a single
text box inside of a UI window. This one is just for text.
Is the UICanvasWindow
https://github.com/MyreMylar/pygame_paint/blob/master/ui/ui_canvas_window.py
in the Pygame Paint project which uses the UIScrollingContainer
https://github.com/MyreMylar/pygame_gui/blob/main/pygame_gui/elements/ui_scrolling_container.py.
With it you can have any UI element in a vertical and/or horizontal
scrolling area. This project doesn't work particularly well in pygame 2 at
the minute, but that's not because of the scrolling area.

Basically as you've discovered the scroll bar on it's own is not enough,
you need to connect it to an area to scroll which can get quite complicated
which is why I have built it in automatically to the text box and to the
scrolling container. I would guess that you should be able to stick
multiple scrolling or non-scrolling text boxes inside of a scrolling
container, though I haven't built out UIs that are that complicated yet
myself.
For various reasons automatically changing the size of the scrolling area
based on the contents isn't always desirable but I suspect there will
eventually be a variant of the scrolling container, or an option, that
enables a more limited scrolling container that does expand to the right
and left if things are placed outside of it's boundaries. Though changing
the scrollable area yourself is not that hard. see:
self.scrolling_container.set_scrollable_area_dimensions((new_width, new_height))
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MyreMylar/pygame_gui/issues/149#issuecomment-657550527,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQORTFNEQVJJGEWQADS7JTR3MBQ7ANCNFSM4OXOWXIA
.


On Chrome, the translate box pops up

For some reason, Chrome thinks that the site is in Italian and should be translated. This just started happening with the introduction of the changelog modal.

No longer experiencing this issue. I have no idea what caused it or what fixed it.


npx knex migrate:list doesn't print a readable list of completed migrations files

Environment
Knex version: 1.0.1
Database + version: PostgreSQL 12.7
OS: macOS 11.6.2
Bug

npx knex migrate:list

produces
[object Object]
[object Object]
[object Object]
No Pending Migration files Found.

Previous version (0.95) listed the filenames of completed migrations:
20220119154150_x.ts
20220119155840_y.ts
20220120081602_z.ts
No Pending Migration files Found.

Error message

No error message, just a bit inconvenient to read :)

Reduced test code, for example in https://npm.runkit.com/knex or if it needs real
database connection to MySQL or PostgreSQL, then single file example which initializes
needed data and demonstrates the problem.

Run npx knex migrate:list with at least one completed migration.
I think the fix is to say completed[i].name here https://github.com/knex/knex/blob/1744c8c2655a8362260ba987d706ec3473681a78/bin/utils/migrationsLister.js#L16

Will be fixed in 1.0.2, sorry!

Will be fixed in 1.0.2, sorry!

No worries, thanks for doing this!

I'm on version 1.0.3 and am still encountering the issue.
> npx knex migrate:list
Requiring external module ts-node/register
Found 3 Completed Migration file/files.
[object Object]
[object Object]
[object Object]
No Pending Migration files Found.

Thanks.

v1.0.4 still has this issue :/

Released in 1.0.5

Currently in 1.0.7 and still having this issue

Same issue here i'm using next 13.4
Found 1 Completed Migration file/files.
[object Object]
Found 8 Pending Migration file/files.
[object Object]
Found 8 Pending Migration file/files.```


please add AWS to validated VPN device table

[Enter feedback here]
Please consider to add AWS VPNGW in validated VPN device. Of course, it is not a physical device, but this info is very helpful for users to check supportability on VPNGW.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 779fbece-f67b-28ef-143e-f58ecfa29b1d
Version Independent ID: fe532684-022f-9006-9179-c534fd923171
Content: About VPN devices for connections - Azure VPN Gateway
Content Source: articles/vpn-gateway/vpn-gateway-about-vpn-devices.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

we have a public document about S2S connection to AWS
https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-aws-bgp

@kikawash  Thanks for the feedback. We will engage the content development team for further investigation, they will verify and perform necessary changes in the document as needed.

#reassign:deeharris-23