Conversations involving multiple participants, allowing collaboration and information sharing in Teams
This portion of my example script:
#HotIf WinActive("ahk_exe ms-teams.exe")
will limit this hotkey to ONLY swap the keymapping within teams.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am often working in other windows but have a lot of teams messages that I need to address. This results in my sending meaningless messages accidentally when I hit ENTER thinking I am in a different window but I am really in teams. How do I by default prevent the ENTER button from sending a message?
Conversations involving multiple participants, allowing collaboration and information sharing in Teams
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
This portion of my example script:
#HotIf WinActive("ahk_exe ms-teams.exe")
will limit this hotkey to ONLY swap the keymapping within teams.
Thank you! Your simple response was spot on!
What do you mean by format mode?
Are you talking within the context of Windows?
Even the question doesn't seem to explain the context.
Are we talking about web apps running within a browser?
If that is the case, then change should be easy to implement by the developer an₫ be part of the settings:
In cross platform javascript an "on_event" function can detect the key pressed from then on it is a simple if then statement.
I really don't understand why the site owners & developers make such a big deal out of it.
I wrote an extension for Youtube that does the same sort of thing. The same can be don't for apps like WhatsApp.
My question is WHY it isn't?
It is a real pain in Open AI's chatGPT relevant portals. It is ridiculous. There must be a reason for it. In fact, Co-pilote on the sidebar of Edge has Enters as line feed as default which should be the case for all chat boxes.
Now you are referring to format mode that I am intrigued about. So, can you please give me details.
I might be able to change it using programming, but I don't have the time, and it shouldn't be me but the site owner and the responsible developers to do it.
This is something pointed out by someone. You might have already responded to it, but I came across your first response from someone who has managed to do it. Therefore, I apologise, and I would be grateful at least send me a link to your previous explanations, if any.
Thanks
I noticed that copilote opened as side widow in Edge actually doesn't use return key as send.
So why not change it everywhere? Open AI even professional part still has the same problem. For a web app it must be even easier, unless the basic on event javascript can't tell if the key is sent or return.
So why don't they do it?
This is starting to sound sinister.
I just made a new modal interface for my car. It has normal mode, and hill mode. Toggle by clicking the mode button next to the start/stop button.
In hill mode, press the accelerator to slow, and the brake pedal to accelerate. There will be a light just behind the steering wheel to tell you what mode you are in. I recommend looking at the road while you drive.
This is how using 'shift+enter to linefeed', except when it is 'enter to linefeed' feels to me.
A less extreme metaphor: there are vi, emacs, and notepad people. Each gets used to their interface and it becomes physical memory. Very very few of them toggle back and forth on a paragraph to paragraph basis - that way lies madness.
In the mobile app, there is no issue using two separate keys to perform these independent functions regardless of input mode. Surely a more consistent customer feel would be achieved by giving an option to change this default functionality.