Skip to content

Commit

Permalink
some todo notes
Browse files Browse the repository at this point in the history
  • Loading branch information
zadjii-msft committed Feb 28, 2023
1 parent fa1140d commit 01388c9
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 2 deletions.
4 changes: 4 additions & 0 deletions src/cascadia/TerminalApp/TerminalPage.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -4504,6 +4504,10 @@ namespace winrt::TerminalApp::implementation
// We're going to be asked for this.
_stashedDraggedTab = tabImpl;

// TODO! Stash the offset from where we started the drag to the
// tab's origin. We'll use that offset in the future to help
// position the dropped window.

// Into the DataPackage, let's stash our own window ID.
const winrt::hstring id{ fmt::format(L"{}", _WindowProperties.WindowId()) };

Expand Down
6 changes: 4 additions & 2 deletions src/cascadia/WindowsTerminal/AppHost.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -1214,18 +1214,20 @@ void AppHost::_handleMoveContent(const winrt::Windows::Foundation::IInspectable&
// The WindowPosition is in DIPs. We need to convert it to pixels.
const til::point dragPositionInDips{ til::math::rounding, args.WindowPosition().Value() };
const auto scale = _window->GetCurrentDpiScale();

const til::point dragPositionInPixels{
til::math::rounding,
dragPositionInDips.x * scale,
dragPositionInDips.y * scale,
};
};

// Fortunately, the window position is already in pixels.
const til::rect windowBoundsInPixels{
_window->GetWindowRect()
};

// TODO!: adjust for the non-client bounds

// Use the drag event as the new position, and the size of the actual window.
winrt::Windows::Foundation::Rect rect{ static_cast<float>(dragPositionInPixels.x),
static_cast<float>(dragPositionInPixels.y),
Expand Down

1 comment on commit 01388c9

@github-actions
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@check-spelling-bot Report

🔴 Please review

See the 📜action log for details.

Unrecognized words (3)

corewindow
curremt
fragement

Previously acknowledged words that are now absent CLA demoable DUMMYUNIONNAME everytime Hirots inthread ntsubauth NTWIN OPENIF OPENLINK PCLIENT PCOBJECT PCUNICODE PNTSTATUS PPROCESS PUNICODE reingest unmark :arrow_right:
To accept ✔️ these unrecognized words as correct and remove the previously acknowledged and now absent words, run the following commands

... in a clone of the git@github.com:microsoft/terminal.git repository
on the dev/migrie/oop/3/an-unexpected-party branch (ℹ️ how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/v0.0.21/apply.pl' |
perl - 'https://github.com/microsoft/terminal/actions/runs/4294953316/attempts/1'
✏️ Contributor please read this

By default the command suggestion will generate a file named based on your commit. That's generally ok as long as you add the file to your commit. Someone can reorganize it later.

⚠️ The command is written for posix shells. If it doesn't work for you, you can manually add (one word per line) / remove items to expect.txt and the excludes.txt files.

If the listed items are:

  • ... misspelled, then please correct them instead of using the command.
  • ... names, please add them to .github/actions/spelling/allow/names.txt.
  • ... APIs, you can add them to a file in .github/actions/spelling/allow/.
  • ... just things you're using, please add them to an appropriate file in .github/actions/spelling/expect/.
  • ... tokens you only need in one place and shouldn't generally be used, you can add an item in an appropriate file in .github/actions/spelling/patterns/.

See the README.md in each directory for more information.

🔬 You can test your commits without appending to a PR by creating a new branch with that extra change and pushing it to your fork. The check-spelling action will run in response to your push -- it doesn't require an open pull request. By using such a branch, you can limit the number of typos your peers see you make. 😉

If the flagged items are 🤯 false positives

If items relate to a ...

  • binary file (or some other file you wouldn't want to check at all).

    Please add a file path to the excludes.txt file matching the containing file.

    File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

    ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

  • well-formed pattern.

    If you can write a pattern that would match it,
    try adding it to the patterns.txt file.

    Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

    Note that patterns can't match multiline strings.

Please sign in to comment.