* [FancyZones] Set correct corner preference when snapping windows on Windows 11
* Changed magic numbers to use enum values.
* Added missing words to spell check list.
* Changed note: to todo: for future visibility
* Changed note: to todo: for future visibility
* Update nuget packages
* try to fix build (Microsoft.UI.Xaml)
* Removed dlls because there are not needed anymore
* Add binaries System.Text.Json.dll (5x) to wxs file
* Downgrade System.IO.Abstractions.* due to breaking changes
* Update Microsoft.NET.Test.Sdk
* Revert MSTest.* to 2.2.3
* remove unnecessary sdk
* add .vsconfig to sln, remove dead link
* spell check
* Update WindowsTargetPlatformMinVersion to 18362 (Minimum required version in README.md)
* Update release.yml
* Update ColorPickerUI.csproj
* Update release.yml
adding in .net6 sdk and moving stuff sooner
* Update release.yml
* Update release.yml
* fixing test
* Forcing vs17 and adding in .net 6 sdk
* forcing pool
* fixing issues in each pipeline
* moving release .net up
* fixing diff on agent version for nuget installer
* Removing system.text.json.dll as included now
* getting unit tests it looks like to work
* updating everythign to .net 6 minus wxs for runtime
* unit test still have
* getting 6.0 stuff up and going. Terminal Unit tests have file max length issue ....
* found i think the last .net 5 issue
* looks like i wasn't aggressive enough with the 6.0 upgrade
* Getting stuff .net 6 buildable again
* tweaking with new stuff for installer
* Update newly added merged projects to .net 6
* Fix HeatDirectory bug on VS 2022
* Settings still needs JSON dependency
* Revert "getting 6.0 stuff up and going. Terminal Unit tests have file max length issue ...."
This reverts commit b9cb4586dc.
* Update sln version
* supress obsolete warning, since this is not a new development
* Partially Revert "Getting stuff .net 6 buildable again"
This reverts commit 42b4201c6b.
* supress another obsolete warning, since this is not a new development
* Reduce the unit test project name to avoid MAX PATH in CI
* Upgrade project's toolset in the main solution
* Some TODOs to review HttpClient usage
* Upgrade project toolsets from other solutions
* Install .net 6 instead of .net 5
* Fix issue when disabling PowerToys Run on .net framework 6
* Update docs for Visual Studio 2022
* PR comments: manually upgrade missing VS 2019 references
* Discard no discard values to solve compiler warnings
Co-authored-by: Jaime Bernardo <jaime@janeasystems.com>
* Edit layout dialog title fix
* Added TextBlock in the contentdialog title to enable TextTrimming
* Fix text trimming and wrapping
* Too long name doesn't affect dialog width
Co-authored-by: niels9001 <niels.laute@live.nl>
* excluding launcher from fancy zones setting GWL_STYLE WS_POPUP
fix WS_POPUP type
* Migrate spelling-0.0.19 changes from main
* rebase fix
* fix spellcheck
Co-authored-by: Dustin L. Howett <duhowett@microsoft.com>
* [FancyZones] Remove obsolete code
The field `m_zoneSets` is unused, and may be removed.
* [FancyZones] Remove obsolete code
The field `m_windows` is unused, and may be removed.
* [FancyZones] Move adjustment of `RECT` to utils.cpp
By doing so, also fix a bug where a non-`WS_SIZEBOX` window (a window that should not be resized) was resized (and not properly resized) if it was zoned into more than one zone.
* [FancyZones] Complete rename `ZoneWindow` -> `WorkArea`
Fix leftovers from "[FancyZones] Rename ZoneWindow -> WorkArea (#12223)"
* [FancyZones] Refer to the move/size action as dragging
* [FancyZones] Rename `ActiveZoneSet` -> `ZoneSet`
There is only one zone set used by a work area.
* [FancyZones] Rename `zoneUuid` -> `layoutUuid`
The variable holds the UUID of the layout (not of a zone).
Co-authored-by: float4 <float4-unspecified-mail>
* Add logging for PowerRename
Move call tracer to common/utils/logger
Add logging to both PowerRename dll and PowerRenameUIHost
Add PowerRename to BugReportTool event viewer collection
* Log more errors and exceptions
* [Telemetry] Add basic interaction events to FZ
Adds some basic interaction events to FancyZones, such as:
- Starting the drag Window movement.
- A newly created window snapping to a zone.
- Using the Keyboard to snap or extend to a zone.
* Update src/modules/fancyzones/FancyZonesLib/FancyZones.cpp
Co-authored-by: Seraphima Zykova <zykovas91@gmail.com>
* Update trace.cpp
* Rename EventSnapNewWindowIntoZone
* Adjust event names according to PR feedback
Co-authored-by: Seraphima Zykova <zykovas91@gmail.com>
* updated virtual desktop retrieving
* save with null-guid
* moved guid utils
* moved DeviceIdData related functions
* replaced strings with data structs
* default value
* clean up
* save app zone history with zones settings
* compare with null guid
* updated tests
* refactoring
* logs
* sync vd ids
* logs
* refactoring
* check virtual desktop id
* OnDisplayChange call
* compare device ids in editor
- Ctrl+Tab to switch between zones and layout overlay window
- Tab to focus between grid zones and resizers
- While resizer is focused: arrows to move it; Del to remove it
- While zone is focused: (Shift)+S to split it horizontally/vertically
* Custom button with automation event on click
* Rename MyButton to ClickAutomationEventButton
* Rename property to OnClickAutomationValue
* Remove unneeded line
* fix(#11125): fallback to canonical regkey session unaware
* chore(#11125): use wil::unique_hkey instead of HKEY for fallback CurrentVirtualDesktop
* refactor: extract new explorer current virtual desktop behavior into a separate method
* Started work on algorithm to select the zone with the center closest to the cursor.
* Fixed algorithm to compute center of rectangle
* Revert to taking the smallest area when the centers are too close (75 pixels).
Temporary turned off buffer of window selection to better see how the algorithm is working.
* Remove change to sensitivity radius.
* Changes in response to SeraphimaZ's comments.
* spelling fix
Co-authored-by: ulazy1 <ulazy198@gmail.com>
* fixing first set of host of bugs
* objects are already set to defaults
* shifting to string.is null / empty
* setters
* fixing stylecop oops
* checking in the FxCop dep but commenting it out for easier coming back
