Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Mouse without borders #77

Closed
Dr-Flay opened this issue May 12, 2019 · 96 comments
Closed

Mouse without borders #77

Dr-Flay opened this issue May 12, 2019 · 96 comments
Labels
Idea-New PowerToy Suggestion for a PowerToy

Comments

@Dr-Flay
Copy link

Dr-Flay commented May 12, 2019

I see the MS Garage project "Mouse without borders" is not here in github.
I think this is in every way an essential PowerToy for people with multiple Windows systems.
Maybe it could also serve as a solution to another request for multiple mouse support.

@cowens
Copy link

cowens commented May 12, 2019

Even better, add multi-OS support. Synergy is showing it's age and Logitech's solution is pretty bad to.

@jaimecbernardo jaimecbernardo added the Idea-New PowerToy Suggestion for a PowerToy label May 13, 2019
@CaryRW
Copy link

CaryRW commented May 13, 2019

I completely agree. I use Mouse without Borders every single day. An outstanding utility, but would be amazing with MacOS support. I hate Mac's, but must have one for testing purposes. I do use Logitech's solution, but to say it is "pretty bad" is an understatement of epic proportions. It's time for MWB to take it to the next level. PLEASE!!!

@BubiBalboa
Copy link

I'm glad I'm not the only one who had this idea.

MWB desperately needs some development and better communication and this would be the perfect place for both.

Thoughts, @indierawk2k2 ?

@TonyGravagno
Copy link

+1 Came here for the exact same reason. Please FOSS MWB.

@mbrittenham
Copy link

This absolutely needs to be built as a PowerToy. This is a key tool for my day to day work.

ryanbodrug-microsoft pushed a commit to ryanbodrug-microsoft/PowerToys that referenced this issue Apr 14, 2020
ryanbodrug-microsoft pushed a commit to ryanbodrug-microsoft/PowerToys that referenced this issue Apr 14, 2020
* Added fix for closing wox on pressing escape and app execution

* Added fix to prevent autosuggestbox resize
traies added a commit that referenced this issue Apr 28, 2020
* minor modifications in README

* Added launcher project and changed references to common

* Added the code to launch another process

* added shellapi header

* Added launcher to runner

* added functions to remove the abstract class error

* added the wox launcher dll

* Readded the reference to common

* modified the additional include directories for the release version

* changed the name to be displayed from Wox.Launcher to Launcher

* Localized the strings of Launcher

* Added a SearchResult Helper class

* Created a helper class to use indexer and return search results

* Added the main and settings file which declare most of the plugin interfaces

* Added references and renamed a class

* Added the images folder which contains the windows indexer icon

* Added the image

* Added the plugin.json file

* Minor changes in project files

* Added plugin.json to the project

* Modified the output paths to create the dll for the plugin in the correct location

* Refactored the code to make it unit testable

* Made the code unit testable and added unit tests for the indexer plugin

* Removed commented out code

* Code to terminate wox when we exit PowerToys

* Copy from Jeremy's fork PR

* Removed unnecessary plugins from source tree

* add missing files

* Fix postbuild event

* Added x64 for all Wox project - Debug mode

* Removed the AnyCPU config - Debug

* Added the build paths for release x64 (removed AnyCPU)

* Set warning level to 4 : Release

* Set warning level 4 : Debug

* set optimize code to false

* Removed notify icon component

* Removed setting UI XAML file and references

* Readded necessary callback functions

* Removed python path and python plugin functions

* Removed UI related to python path and the bindings related to that

* Remove python bindings

* Removed the localized string translations from pythonDirectory and SelectPythonDirectory

* Manually resolving conflicts

* Fix Wox build in project settings

* deleting unused project files

* Undo change internal

* Fix internal variable

* All wox exceptions in debug are getting rethrown, and thus causing the app to crash.  This change removes the debug specific code and allows exceptions to be handled the same was as release.

* Ported Indexer plugin to .net core 3

* Added the test project back

* Removed the .net framework indexer folder

* readding the plugin.json file

* Changed the anyCPU config to x64 for windows indexer plugin

* Adding dependency to wox project on the runner.  This should make sure the wox.exe can be build and launched by the runner so wox can run as a background process.

* Updating build dependencies.  Wox.Launcher wasn't built as part of the F5 Experience, and nor were the plugins

* removing locks from the ResultListBox code behind file.  All callbacks are accessed from the Main/UI thread.

* Remove anyCPU config and changed it to x64

* Removed anycpu of test proj

* Adding dependency

* Renaming executable to PowerLauncher.  Replaceing icons with placeholder. Deleting Docs folder

* Renaming AppData directory from 'Wox' to 'PowerLauncher'.  Also replacing issue link with powertoys github.

* adding support for xaml islands

* Added Neils UI code

* Replace Niels Code references

* Added assets and behaviours

* Add missing reference

* Add main view model binding

* Using proper executable name when closing 'PowerLauncher' process

* changed x:bind to Binding to avoid reference

* Updated bindings for launcher

* Added binding on searchBox

* Adding Directory.Build.targets file to kill the PowerLauncher pprocess on Build or Clean operations of all 'Launcher' projects.

* Fixed exception preventing result display

* Fixed issue with wpf marshalling events to a non UI thread

* Optimised result binding by inserting search result from multiple plugin in parallel

* copy resource files to output folder

* Corrected the output path for the indexer plugin

* windows indexer plugin is working

* Remove console print statement

* Added callback function for mouse click on search result

* Working App execution

* Cherry picked pinyin performance changes from jjw24's master branch

* change nuget package to msft for winrt compat

* Working up/down arrow key

* updating references and removing a few that seem uneeded for how stuff is referenced

* adding two back in

* Removing Squirrel dll.  unsure on updating so i kept that logic in

* Updated functionality on suggestion chosen in autosuggestbox

* Added the <useWPF> tag to remove the warning

* Removed an unnecessary <useWindowsForms> tag

* Removed the item group for properties from calculator plugin

* Removed the item group for properties from folder plugin

* Removed the item group for properties from indexer, program and shell plugin

* Removed itemgrp from wox.core and wox.test csprojs

* Removed the unnecessary wox files to clean up codebase

* Renamed Wox.Plugin.Indexer to Microsoft.Plugin.Indexer

* Renamed Wox.Launcher to Microsoft.Launcher

* To avoid DBNull to String typecast exception

* Added query submitted event to handle default action on clicking a list view item

* Merge pull request #42 from microsoft/AddPinyinPerformance

Cherry picked pinyin performance changes from jjw24's master branch

(cherry picked from commit b9e437c)

* Rectyfying title display

* Title display working correctly

* Removed .yml files

* adding checks

* Making wox.csproj build wox assembly instead of powerlauncher

* Removing update logic from PowerLuanch App.xaml.cs as was done in Wox project.

* Making Query internals visible to wox.

* Update Powerlauncher nuget packages to be same version as wox.csproj.   Note:  FoxyWeavers.xsd change is automatically done as part of nuget package update.

* Updating build dependencies to so that wox.launcher depends on powerlauncher.csproj not wox.csproj

* Removing 'Wox' branded logos from powerlauncher.csproj as was done previously or wox.csproj

* Downgraded the library to the latest stable version

* single thread execution of the indexer plugin and InvalidOperationException due to connection being closed on ExecuteReader, handled separately

* Modified the test, the connection need not be null after being disposed. There is no direct way of checking if an object has been disposed other than to throw the InvalidOperationException

* Removing x86,ARM,ARM64, build configurations, as these were added accidentally when adding xaml island support.

* Removed STAThread

* Modified the output folder produced

* Renamed the dll produced

* Added dependency on PowerLauncher to the Microsoft.Launcher project

* modified the name of the dll in the indexer plugin

* Ignoring 128 errors from taskkill, as this means the process isn't running. We don't want htis to show up in the warnings list on build

* Added fix for closing wox on pressing escape and app execution (#75)

* adding useWPF to get rid of warning

* Launcher resize issue on selecting search result (#77)

* Added fix for closing wox on pressing escape and app execution

* Added fix to prevent autosuggestbox resize

* Fixing xaml catastrophic failure, based on Miguels suggestion here: CommunityToolkit/Microsoft.Toolkit.Win32#210

* suggested fix

* removing unused mutex string

* Searches for keyword only in title and not content to improve the quality of results

* Display the title from System.Title directly instead of extracting it from the path

* Removed additional README instructions before moving to the powerToys repo

* Fix Query builder test (#86)

* Revert base viewModel class to fix tests.

* Removing unused post build and deploy scripts.

* tweaked url

* Update plugin.json

* Update README.md

* removed unused dep (#2080)

* removed reference to everything (#2133)

* SearchIndexer - Modifying QueryContentProperties and QuerySelectColumns to use System.FileName

* Search result thumbnail for PowerLauncher (#2124)

* Replace WPF Imaging library with UWP

* Removed UWP and WPF namespace conflicting files from Wox

* Removed Image hashing as it wasn't used anywhere

* Updated formatting

* Set MainViewModel visibility to hidden on startup

* Enable CI build on PowerLauncher Branch (#2181)

* Enable CI build on PowerLauncher Branch

* Updated Nuget restore to latest and added AssetTargetFallback property

* tweak text (#2177)

* [Window Walker] Migrate to Launcher (#2093)

* Copy the existing calc. plugin foldeR

* Blindly rename a bunch of things to Window Walker

* Update the solution to reference the new plugin

* Get basic Yo returned

* Remove all the languages except english

* Lower quality of icon as well as test showing it

* Add the core non-ui parts to the plugin

* Delete calculator png

* Get it to compile

* Added the actual code which apparently doesn't work

* Finally start showing results

* Fix up strings

* Switch working

* Remove unused classes

* Remove unneeded async

* Added MSI support for Launcher (#2242)

* Fixed typo in output folder of calculator plugin

* Calculator plugin works

* Modified the name of the image to remove space as space is assumed to be a separator in wcx file

* Fixed typo in calculator dll

* Fixed typo in calculator plugin

* Shell, Program, Folde and indexer plugin working

* Added the ww plugin

* Fixed typos in the calculator plugin

* Delete file that was added unintentionally

* revert calculator rename changes

* Reverted other files changed

* Reverted renaming of file with space

* Pull changes from master to dev/powerLauncher (#2255)

* Dpi unaware placement bug (#2121)

Fix for bug when placing dpi unaware window such as Notepad++ in left of right part of monitor. In that application gap of about 7px was left or right.
This fixes only single-monitor scenario
It skips correction for dpi unaware window that leaves a gap

* Move markdown parsing logic outside control thread (#2099)

* Move markdown parsing logic outside control thread

* Update MarkdownPreviewHandlerControl.cs

* Remove trailing whitespace.

That'll teach me for trying to make an edit from the GitHub page.

* Migrate power rename MRU lists from registry to JSON (#2090)

* Handle most recently used search/replace strings within settings.

* Check for last modified time of json file and reload it if needed.

* Handle changes in MRU search / replace lists size.

* Improve handling of changes in MRU list size.

* Don't check for last modified time in every getter method. Load only when starting application.

* Add const identifier to getter methods.

* Address PR comments: Add const to reg and json file paths and set them in constructor initializer. Check pushIdx validity. Move implementation to cpp of PowerRenameUI constructor.

* Add error checking when getting values from registry.

* Implementing changes suggested in #1992 (#2116)

* Implementing changes suggested in #1992

* Update Product.wxs

Co-authored-by: Ebenezer Ewumi <ebenezer.ewumi@wsu.edu>

* Fix for issue #1532 - [PowerToys tray icon] Show version on tooltip (#2117)

* Fix for issue #1532

[PowerToys] Show version on tooltip

* Update src/runner/tray_icon.cpp

Co-Authored-By: Andrey Nekrasov <yuyoyuppe@users.noreply.github.com>

Co-authored-by: Andrey Nekrasov <yuyoyuppe@users.noreply.github.com>

* FZ editor: Splitted zones positioning (#2158)

* Added a mutex to ZoneWindow, ensured no data races occur (#2154)

* Added a mutex to ZoneWindow, ensured no data races occur

* Protected draggedWindow* members with a mutex

* Ensured that critical reads happen in a single transaction

* Dpi unaware placement bug - multimontior with same DPI settings fix (#2156)

* Dpi unaware placement bug - multimontior with same DPI settings fix

* Using different enumerating method

* Changed AllMonitorHaveSameDpiScaling method

* Removed accidental file

* small rename

* Changed some methods to CamelCase

* Review comments fixes

Co-authored-by: PrzemyslawTusinski <61138537+PrzemyslawTusinski@users.noreply.github.com>
Co-authored-by: Ben Randall <veleek@gmail.com>
Co-authored-by: vldmr11080 <57061786+vldmr11080@users.noreply.github.com>
Co-authored-by: eduardodextil <55205162+eduardodextil@users.noreply.github.com>
Co-authored-by: Ebenezer Ewumi <ebenezer.ewumi@wsu.edu>
Co-authored-by: Nghia M. Luong <32159519+sqrlmn@users.noreply.github.com>
Co-authored-by: Andrey Nekrasov <yuyoyuppe@users.noreply.github.com>
Co-authored-by: Seraphima Zykova <zykovas91@gmail.com>
Co-authored-by: Ivan Stošić <ivan100sic@gmail.com>

* Somil55/merge custom ui into launcher (#2271)

* Remove Autosuggest box (#2192)

* Update Settings.Designer.cs

* Revert "Update Settings.Designer.cs"

This reverts commit a1bc0dd.

* Updated LauncherControl XAML to add textbox and listview

* List View displayed

* Hooking up execution on the selected index, removing two way binding on selection, and experimenting with popup that doesn't work

* Updated MainViewModel to Remove context menu and history

* Added Resultist XAML Island project

* Updated SelectedItem and SelectedList Binding.
Issues :  List box doesn't open when query is written for first time but opens in subsequent queries.

* 1. Mouse Click working
2. List View is can't be focused
3. Fixed width of Launcher

* Removed two way QueryText box binding

* Removed SelectedItem two way binding and replaced with a callback

* [Cleaning] Remove redundant UWP project

* [Cleaning] Updated files to keep only atomic changes against dev/powerLauncher

* Thmbnail fixed for NEW UI

* Removed PreviewMouseDown function required by older WOX code

Co-authored-by: ryanbodrug-microsoft <56318517+ryanbodrug-microsoft@users.noreply.github.com>

* Added the auto-complete feature

* Removing ContextMenuPluginInfo, and ContextMenuTopMost as these commands are not used int the new design.

* Fixed merge conflicts

* Set only when index is 0

* One way binding

* Removed unnecessary binding

* Deleting unused (commented out code) that was legacy from wox project.

* Binding Buttons to appropriate context menu commands.
1. Buttons are dynamically loaded in a listview based on the actions supported be each plugin.

This change also deletes unused commands.

Note:  Most button events don't seem to be getting routed to the Selected Item.  Currently using 'PointerEntered' to validate the behavior.  The actions should be trigged by the button command property in the future.

* manually handling tab in mainwindow

* Loading context buttons on Selecting a suggestion list item

* Allowing hover event to load content menu items and display them as well.

* Adding context buttons to Indexer plugin.  This allows for the following:
1. [Files] Open Containing folder
2. [Folders/Files] Copy Path

* Remove White background of list (#2218)

* Remove white background of list

* Removed comments

* Changed to ContainerContentChanging event

* add const variables instead of numbers

* Added comment before the updatelistSize function

* Search box UI (#2224)

* Added backdrop and rounded corner

* Fix for two alt+space press to bring searchbox issue

* Fixed merge conflict

* Clean Mainwindow.xaml code

* Fix for textbox focus on first visible

* Allowing users to tab between the context buttons for the selected resut.  Also allowing users to press 'enter' to action on the selected items.

* Renaming SelectedIndex to ContextMenuSelectedIndex

* Enabling key accelerators on context buttons.
1. Add new object ContextMenuResult instead instead of reusing Result for both query results and context menu results.
2. Binding KeyboardAccelerator keys to contextmenuitemviewmodel
3. Enabling and disabling contextmenu items when selecting or deselecting each row.  Because we are manually maintaining selectionwe can't use ScopeOwners as the textbox is really the only item ever in focus.

* Launching explorer instead of the UWP application when selecting 'open file location'.

* Added fix for border showing up when result count is zero

* Updated fix for border on no result

* Adding visibility  after clearing result in MainViewmodel

* Launcher Light/Dark mode (#2235)

* Fixed issue with list view background not updating with Windows theme change

* Added theme change for WPF

* updated ShadowDepth for dropshadow

* Updated border thicknes of searchbox and listview

* Diff issue with ResultList.xaml

* Removed change in result delay

* Added code to pull colors from UWP

* Updated border resource to use system based SystemControlHighlightAccentBrush

* Updated corner radius in dark mode

* Updated Launcher description text

Co-authored-by: ryanbodrug-microsoft <56318517+ryanbodrug-microsoft@users.noreply.github.com>
Co-authored-by: Alekhya Reddy <reddykalekhya@gmail.com>

* Changed to SystemChromeLow from Accent brush (#2272)

* Removed ListView animations

* Positioning ContextButtons and adding background.

* Disabling scrollbars for gridview items.

* Removed folder plugin

* removed deployment for uwp apps (#2298)

* Simulating Win+backspace key press, instead of Win+Control as it was launching WW (#2250)

* text is selected whenever launcher gets hidden and is then set to visible (#2315)

* Update nuget packages across solution to latest (#2334)

* simplifying the xaml and making things tighter (#2327)

* Setting runcommand as the default execution method, and turning off run as admin by default.

* Opening explorer if the user has types a file path.

* Enable PowerLauncher toggle

* Launcher MSI - Added a required dll and removed folder plugin (#2355)

* Modified the product.wxs file

* Added the x64 config

* Modify scoring algorithm for fuzzy search (#2361)

* Modify scoring

* modified to if else

* Fixes race conditions with PointerEnter/Exit events conflicting with Selection and unselection.   This change provides better encapsulation of the logic to enable a selected item for accelerator (hotkey) events, and allow mouse input on results where the pointer is over.

* Fixes an issue where PointerExit would hide the selected context buttons.

* Result List - Bad rebase overwrote margin and translation fields.

* Fixed process executing on clicking enter if no text in search box

* Codeflow cleanup when selectedItem is not null

* adjusting how programs are displayed. (#2369)

* Removing description from title

* adjusting subtitle

* removing accidently paste

* removing desc for uwp apps

* Revert "Removed folder plugin"

This reverts commit 064d638.

We will use the folder plugin to better mimic the way the start menu and run prompt deal with directories

* Updating JetBrains.Annotations to 2020.1.0 to be consistent with other projects.

* Replacing submenu text with full path as 'Ctrl-Enter' doesn't do anything.  Also reducing the String of CreateOpenCurrentResult to fit in one line.

* - Making Open Directory subtitle fixed, and the title as the current directory.

* Adding back binding to QueryText and updating the cursor position similar to how wox originally did it.

* Add the folder plugin wxs back in (#2374)

* Deduping results for program plugin (#2375)

* Removing description from title

* adjusting subtitle

* removing accidently paste

* removing desc for uwp apps

* Getting dups removed from list if LNK exists

* adjusting subtitle

* removing accidently paste

* Getting dups removed from list if LNK exists

* changed to normal forloop

* Removing WinR (#2381)

* Updated program execution to call action on background thread. (#2370)

* PowerLauncher Settings integration

* Added cold start fix (#2385)

* - Fixes cursor jumping around issue.
- Seperating the ability to set the text from initiating a query.
- Plugins have to explicitly request the query be updated.
- Updating Folder plugin to explicty update the query on folder selection.
- Removing unused changes from 'Wox' that don't compile.

* Fixing gap in logic where query was triggering when programatically setting text.

Updating the binding and settext both will trigger the TextChanged event on a seperate event dispatcher.  For this reason we dynamically detect which eventhandler is most approapriate on the textchanging event.

* Updating the QueryText to the selected item when navigating up/down with the  arrow keys.

* Removing action on folder result, and displaying folder path on selecting a folder result from the folder plugin.

* Making folder results from the search indexer plugin behave like folder results from folder plugin.

* Folder Results open the explorer window when selected.

* The Open Current Folder result shouldn't change the query text to 'Open {folder path}' when selecting the results.

* Initializing query text strings.

* Defensive check for QueryText being empty

* Adding file watchers for UWP detecting when apps are installed or deleted and reindexing the uwp apps

* Removing unused namespace.

* Looking at files and not filtering is better because the timer is more likely to reset while an install is happening, preventing uneeded indexing

* Fix project references

* Fix MaxResultsToShow

* Fix Alt + Space display

* Fix settings defaults

Co-authored-by: Alekhya Reddy Kommuru <reddykalekhya@gmail.com>
Co-authored-by: bkudiess <bakudies@microsoft.com>
Co-authored-by: Divyansh <somm14divi@gmail.com>
Co-authored-by: ryanbodrug-microsoft <56318517+ryanbodrug-microsoft@users.noreply.github.com>
Co-authored-by: Barbara Kudiess <bkudiess@me.com>
Co-authored-by: Jeremy Wu <jeremy24wu@gmail.com>
Co-authored-by: Clint Rutkas <clint@rutkas.com>
Co-authored-by: udit3333 <udit3333@gmail.com>
Co-authored-by: Betsegaw (Beta) Tadele <betsegaw.ta@gmail.com>
Co-authored-by: PrzemyslawTusinski <61138537+PrzemyslawTusinski@users.noreply.github.com>
Co-authored-by: Ben Randall <veleek@gmail.com>
Co-authored-by: vldmr11080 <57061786+vldmr11080@users.noreply.github.com>
Co-authored-by: eduardodextil <55205162+eduardodextil@users.noreply.github.com>
Co-authored-by: Ebenezer Ewumi <ebenezer.ewumi@wsu.edu>
Co-authored-by: Nghia M. Luong <32159519+sqrlmn@users.noreply.github.com>
Co-authored-by: Andrey Nekrasov <yuyoyuppe@users.noreply.github.com>
Co-authored-by: Seraphima Zykova <zykovas91@gmail.com>
Co-authored-by: Ivan Stošić <ivan100sic@gmail.com>
@studleylee
Copy link

Mouse without borders source would be awesome. I came here wondering about its security: encryption or anti-ease-dropping features. It's important with all the homework via vpn and this covid craziness. Thanks for all the work you all do!!!

@mdkiefer
Copy link

I would also like to see this open-sourced. I'd like to contribute to fix a bug when I have mixed-resolution displays.

@MOrlassino
Copy link

I agree! Adding Mouse without Boarders to the Microsoft PowerToy applications would be a welcome addition. Being bundled with PowerToys and open sourced would help with it's discovery by those who don't know it's usefulness and allow it to be extended/enhanced. Also, how awesome would it be to use it with a companion Windows 10 on ARM device or the Windows Duo?
Microsoft Garage Mouse without Borders

@BubiBalboa
Copy link

It's pretty discouraging that none of the active collaborators has bothered to comment on this issue.

@crutkas
Copy link
Member

crutkas commented May 17, 2020

We have been pretty transparent on the v1 roadmap. This is something we haven’t had time to investigate.

is the primary ask to make it xplat? Or just OSS it?

@BubiBalboa
Copy link

BubiBalboa commented May 17, 2020

I just thought someone would at least say anything. It's so quiet around MWB that I thought this topic is being avoided intentionally.

For me open sourcing it -in whatever way- would be the most important part. Right now there is no visible development happening despite lots of little bugs and feature requests and no communication either. The poor people are screaming into the void in the support thread.

So however this situation can be fixed would be fine by me. I just thought that it would be the perfect candidate for open sourcing. If as part of PowerToys or as its own project isn't important. People just bring it up here because it would be a good fit and they have a chance of getting heard.

@mdkiefer
Copy link

I agree that open-sourcing it it be the most important part. That way if someone wants to make it cross-platform they can contribute to do so. Whether it is part of of PowerToys or not is unimportant. Unfortunately, the support thread for Mouse without Borders on the Microsoft Garage site has been less than helpful for getting any direction.

@crutkas
Copy link
Member

crutkas commented May 20, 2020

open sourcing stuff that wasn't developed with OSS in mind takes time and discussions. how stuff is supported / tested gets very interesting as well. More so with something like MWB due to what it is.

@crutkas crutkas added this to the Suggested Ideas milestone May 20, 2020
@BubiBalboa
Copy link

I don't think anybody expects you to just throw the code on GitHub tomorrow but it's still good to set the right expectations just in case.

Would be nice if you guys could update this thread from time to time if there's movement behind the scenes. It's been so quiet around MWB that any new info is highly appreciated. Thank you!

@Jay-o-Way
Copy link
Collaborator

Jay-o-Way commented Aug 21, 2020

https://youtu.be/D9u1vX-pvLs
https://www.youtube.com/watch?v=EozeSDeV3Vo

@Dr-Flay
Copy link
Author

Dr-Flay commented Aug 23, 2020

I'll tell you why I posted this.
I don't want to see MWB languish as an abandoned project like so many others (Pro Photo Tools, Bing Virtual Earth) from the experimental side of MS.
By making it OSS it can be maintained indefinitely,

If this functionality was simply integrated into Windows as it should be MS would be forced to maintain it and any security problems that come up, but as a MS Garage app it is disposable, and at best we would get a warning not to use it anymore.

I understand the program was not originally intended to be OSS, but as it was also intended to be not supported anyway, MS and the authors can only gain from this change, as will those who want to keep using it in the future.

@riverar
Copy link
Contributor

riverar commented Oct 5, 2020

What are the use cases for Mouse without Borders?

@theS1LV3R
Copy link

What are the use cases for Mouse without Borders?

I think the website describes it pretty well:

Would you want to have an incredible mouse that can seamlessly move from one machine to another?
Would you want to get rid of the KVM and be more productive working with multiple machines?

Mouse without Borders is a product that makes you the captain of your computer fleet by allowing you to control up to four computers from a single mouse and keyboard. This means that with Mouse without Borders you can copy text or drag and drop files across computers.

@riverar
Copy link
Contributor

riverar commented Oct 5, 2020

No, that website describes how the software works. I'm looking for how people are using the software today, to understand what problems Mouse without Borders solves, why it should be considered as a new PowerToys feature, etc. (To be honest, I'm not sold this feature is needed.)

@mbrittenham
Copy link

The use case for me is very specific. I have multiple machines on my desk. Desktop, Surface Book, other laptops, etc. They are all connected to different monitors. However, I don't have the desk space for the requisite mouse/keyboard combinations to deal with them all nor do I want to think about which one I'm using. I move the mouse as if it were one machine connected to multiple monitors and no other thinking is required. That, in my opinion, is the core daily driver use case and applies to an all Windows environment. I'm looking for MWB to be OSS and integrated into PoweToys for the continuity of support and roadmap. Right now I'm just living in fear of a breaking change in Windows 10 with no support or path to a fix.

@riverar
Copy link
Contributor

riverar commented Oct 5, 2020

@mbrittenham So for my understanding, you have several monitors, each one (or more) dedicated to other Windows devices, in front of you, right? What are you doing across these devices that necessitates the constant back and forth? What about RDP/VNC? I'm guessing a physical KVM was ruled out due to frequency of switching, is that right?

@watermarkhu
Copy link

@riverar I have a desktop with two monitors from which I work at home and another laptop that I took to the office (when that was still the case). In some cases, two monitors is not enough. While I could buy a third monitor for these cases, more often than not I just take out my laptop. Mouse and keyboard across these two computers makes this workflow seamless.

@mbrittenham
Copy link

@riverar yes, I need to see multiple displays so a KVM won't work and the need to switch is problematic. RDP also requires me to view everything on one machine. This affords me the seamless experience while having multiple machines for the added computing power and redundancy. I may have Teams up on two machines or the same with any of the office apps. I've had Premiere Pro editing and rendering on one system while working email on another and I don't have to context switch anything, even mentally, to go back and forth. However I don't pay a resource tax in my email while rendering video. At the same time I can see all systems simultaneously so if I were to have a monitoring dashboard or some other portal open I can keep it in view which isn't viable with a KVM or RDP session.

@CaryRW
Copy link

CaryRW commented Oct 11, 2022 via email

@smnc
Copy link

smnc commented Jan 28, 2023

Synergy and Barrier are great tools and cross platform. I really would love an open conversation here :)

  1. What makes MWB worthy here with such great other apps like those two (and others)
  2. What needs to be fixed? What are the critical bugs? Lets be targeted.
  3. How critical is MacOS / Linux support for everyone? If we did this, Windows is by default supported but MacOS / Linux are not.
  4. Support for something is going to be hard due to the countless permutations with firewalls, VPN and whatnot. To be transparent, this part worries me is the amount of help / debugging with users we'd have to do to help get people be successful.
  1. The idea of a native-ish Windows KVM alone is worthy. Apple already has this across MacOS and iOS, and I can't see why Windows shouldn't have a similar feature. I'm not banking on it being included in the core OS in the forseeable future, so PowerToys seems like the next best thing for now. MWB itself is great because (1) it's free, unlike Synergy, and (2) once setup, it just works, even before Windows login.

  2. A smoother setup would be huge, it's definitely the highest barrier to entry. The interface is also dated, and intimidating to new users. Current file copying across machines is inelegant. Multi-monitor handling is mediocre. Different mouse speed settings across multiple machines. Lack of native ARM64 support (although emulation works)- if Microsoft is gonna push ARM devices (I love mine), this needs to be fixed.

  3. Honestly? Don't care about multi-OS support. It's a Windows feature, and third party apps exist for people trying to integrate multiple OSes. I just want a native(ish) way to use my mouse across my Windows devices.

  4. MWB works with the native firewall already. For anyone running a 3rd-party firewall it seems simple enough to give instructions to "open port xxxx for local connections, refer to your firewall's instructions for details on how to do this". This is PowerToys, while lowering the barrier to entry should continue to be a focus, expecting a basic level of user compentancy seems reasonable.

@simonstdenis
Copy link

I need a tool that work between my works and personnal machine. Most of clients i've been working with are enforcing a lockdown on local LAN. To make MWB great and usable, I would need some kind of cloud based services to allow device to talk to each other when local LAN is not available.
I'm still using a hardware KVM, which is not great.
Multi-OS would be great, since I have to support MacOS as well.
If there is a copy/paste feature, it must be possible to disable it for DLP purpose.
Additionnal devices should not be tied to a specific tenant or account, since they might also have tenant restriction or personnal account lockdown.
The "server" could be a SaaS and/or self-hosted.

@frodr1k
Copy link

frodr1k commented Feb 21, 2023

I came by to add a +1 on this!

It should either be a PowerToy or a core component of future windows.

@davidfguillaume
Copy link

Would love to have Mouse Without Borders added to Power Toys, it's one of my favourite utilities but quite buggy and showing it's age

@dalfaand
Copy link

dalfaand commented Mar 2, 2023

+1 It should be a PowerToy already!

@andyy0624
Copy link

+1
When I need this feature, what I think of directly is powertoys, how can it not integrate MWB

@crutkas
Copy link
Member

crutkas commented May 23, 2023

🐭⌨️🖱️

@crutkas
Copy link
Member

crutkas commented May 23, 2023

Mouse without borders, now in PowerToys 0.70 🐭🐭🐭

Enjoy

@crutkas crutkas closed this as completed May 23, 2023
@CaryRW
Copy link

CaryRW commented May 23, 2023 via email

@BubiBalboa
Copy link

Mouse without borders, now in PowerToys 0.70 🐭🐭🐭

Enjoy

Fantastic news! Thanks to everyone who made this happen.

Question: Is this now the preferred/official way to install Mouse Without Borders or will the standalone version still be supported?

@CaryRW
Copy link

CaryRW commented May 23, 2023 via email

@lofcz
Copy link

lofcz commented May 23, 2023

This is the greatest addition to PowerToys, ever.

@dpkano
Copy link

dpkano commented May 23, 2023

Nice! Kudos to the team!

@swssr
Copy link

swssr commented May 24, 2023

This is awesome! Amazing work to the team! 🥳🥳

@richard4339
Copy link

Question: Is this now the preferred/official way to install Mouse Without Borders or will the standalone version still be supported?

I'd like to take this question a step further, what (if any) action do those of us who already have the standalone Mouse Without Borders need to do? Is this a full integration and we should uninstall? Is it simply a wrapper and that would cause complications?

@smnc
Copy link

smnc commented May 24, 2023

Question: Is this now the preferred/official way to install Mouse Without Borders or will the standalone version still be supported?

Not one of the devs, but since MWB was last updated more than 2 years ago, I'm betting on the PowerToys version being the one maintained going forward.

@smnc
Copy link

smnc commented May 24, 2023

I'd like to take this question a step further, what (if any) action do those of us who already have the standalone Mouse Without Borders need to do? Is this a full integration and we should uninstall? Is it simply a wrapper and that would cause complications?

I'm not a PowerToys dev, but I can tell you my experiences:
PowerToys won't overwrite or remove your current MWB install, but does use the exact same service - the version of MWB in PowerToys 0.70.0 is just a port of the existing app using the PowerToys interface - so the two version of MWB (PowerToys and stand-alone) will conflict with each other. I uninstalled the stand-alone version and then set up the PowerToys version, and everything worked perfectly.

@Dr-Flay
Copy link
Author

Dr-Flay commented May 25, 2023

Oh that was quick !
I only posted this ticket in May 2019, a mere 4 years ago. How time flies.

@Chaos02
Copy link

Chaos02 commented May 28, 2023

Hey I've been wondering of Mw/oB Source code will be open source some time in the future?
As soon as I knew about it (by being added to PowerToys) I wanted to make an Ubuntu/gnome/Linux port!
Really looking forward to a cross-platform Mouse without borders! (now with 25% less borders!)

EDIT: I just found the source file location... Are there already ports actively being worked on?

@CaryRW
Copy link

CaryRW commented May 29, 2023 via email

@mbrittenham
Copy link

mbrittenham commented Jun 5, 2023 via email

@dsjstc
Copy link

dsjstc commented Mar 6, 2024

EDIT: I just found the source file location

FYI, the relative link posted above seems to link to .../**issues**/src/... The actual source link is:

https://github.com/microsoft/PowerToys/tree/main/src/modules/MouseWithoutBorders

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Idea-New PowerToy Suggestion for a PowerToy
Projects
None yet
Development

No branches or pull requests